Supervised license acquisition in a digital rights management system on a computing device

ABSTRACT

A rendering application on a computing device requests a digital rights management (DRM) system on the computing device to authorize digital content rendering based on a corresponding digital license. If unavailable, the DRM system attempts to silently acquire the license from a license server without the intervention of a user. In the course thereof, the rendering application receives status information from the DRM system relating to the attempted license acquisition thereby and displays the received status information in a rendering application status display portion. If silent acquisition fails, the rendering application hosts a browser, causes the browser to navigate to a license server, allows a user to communicate with the license server by way of the hosted browser to acquire the license, and shuts down the hosted browser upon reception of the license from the license server.

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application is related to U.S. patent application Ser. No.09/290,363, filed Apr. 12, 1999 and entitled “ENFORCEMENT ARCHITECTUREAND METHOD FOR DIGITAL RIGHTS MANAGEMENT”, and U.S. ProvisionalApplication No. 60/126,614, filed Mar. 27, 1999 and entitled“ENFORCEMENT ARCHITECTURE AND METHOD FOR DIGITAL RIGHTS MANAGEMENT”,each of which is hereby incorporated by reference in its entirety.

TECHNICAL FIELD

[0002] The present invention relates to an architecture for enforcingrights in digital content. More specifically, the present inventionrelates to such an enforcement architecture that allows access toencrypted digital content only in accordance with parameters specifiedby license rights acquired by a user of the digital content. Even morespecifically, the present invention relates to supervision of licenseacquisition by a rendering application.

BACKGROUND OF THE INVENTION

[0003] Digital rights management and enforcement is highly desirable inconnection with digital content such as digital audio, digital video,digital text, digital data, digital multimedia, etc., where such digitalcontent is to be distributed to users. Typical modes of distributioninclude tangible devices such as a magnetic (floppy) disk, a magnetictape, an optical (compact) disk (CD), etc., and intangible media such asan electronic bulletin board, an electronic network, the Internet, etc.Upon being received by the user, such user renders or ‘plays’ thedigital content with the aid of an appropriate rendering device such asa media player on a personal computer or the like.

[0004] Typically, a content owner or rights-owner, such as an author, apublisher, a broadcaster, etc. (hereinafter “content owner”), wishes todistribute such digital content to a user or recipient in exchange for alicense fee or some other consideration. Such content owner, given thechoice, would likely wish to restrict what the user can do with suchdistributed digital content. For example, the content owner would liketo restrict the user from copying and re-distributing such content to asecond user, at least in a manner that denies the content owner alicense fee from such second user.

[0005] In addition, the content owner may wish to provide the user withthe flexibility to purchase different types of use licenses at differentlicense fees, while at the same time holding the user to the terms ofwhatever type of license is in fact purchased. For example, the contentowner may wish to allow distributed digital content to be played only alimited number of times, only for a certain total time, only on acertain type of machine, only on a certain type of media player, only bya certain type of user, etc.

[0006] However, after distribution has occurred, such content owner hasvery little if any control over the digital content. This is especiallyproblematic in view of the fact that practically every new or recentpersonal computer includes the software and hardware necessary to makean exact digital copy of such digital content, and to download suchexact digital copy to a write-able magnetic or optical disk, or to sendsuch exact digital copy over a network such as the Internet to anydestination.

[0007] Of course, as part of the legitimate transaction where thelicense fee was obtained, the content owner may require the user of thedigital content to promise not to re-distribute such digital content.However, such a promise is easily made and easily broken. A contentowner may attempt to prevent such re-distribution through any of severalknown security devices, usually involving encryption and decryption.However, there is likely very little that prevents a mildly determineduser from decrypting encrypted digital content, saving such digitalcontent in an un-encrypted form, and then re-distributing same.

[0008] A need exists, then, for providing an enforcement architectureand method that allows the controlled rendering or playing of arbitraryforms of digital content, where such control is flexible and definableby the content owner of such digital content. A need also exists forproviding a controlled rendering environment on a computing device suchas a personal computer, where the rendering environment includes atleast a portion of such enforcement architecture. Such controlledrendering environment allows that the digital content will only berendered as specified by the content owner, even though the digitalcontent is to be rendered on a computing device which is not under thecontrol of the content owner.

[0009] Further, a need exists for a trusted component running on thecomputing device, where the trusted component enforces the rights of thecontent owner on such computing device in connection with a piece ofdigital content, even against attempts by the user of such computingdevice to access such digital content in ways not permitted by thecontent owner. As but one example, such a trusted software componentprevents a user of the computing device from making a copy of suchdigital content, except as otherwise allowed for by the content ownerthereof.

SUMMARY OF THE INVENTION

[0010] The aforementioned needs are satisfied at least in part by anenforcement architecture and method for digital rights management, wherethe architecture and method enforce rights in protected (secure) digitalcontent available on a medium such as the Internet, an optical disk,etc. For purposes of making content available, the architecture includesa content server from which the digital content is accessible over theInternet or the like in an encrypted form. The content server may alsosupply the encrypted digital content for recording on an optical disk orthe like, wherein the encrypted digital content may be distributed onthe optical disk itself. At the content server, the digital content isencrypted using an encryption key, and public/private key techniques areemployed to bind the digital content with a digital license at theuser's computing device or client machine.

[0011] When a user attempts to render the digital content on a computingdevice, the rendering application invokes a Digital Rights Management(DRM) system on such user's computing device. If the user is attemptingto render the digital content for the first time, the DRM system eitherdirects the user to a license server to obtain a license to render suchdigital content in the manner sought, or transparently obtains suchlicense from such license server without any action necessary on thepart of the user. The license includes:

[0012] a decryption key (KD) that decrypts the encrypted digitalcontent;

[0013] a description of the rights (play, copy, etc.) conferred by thelicense and related conditions (begin date, expiration date, number ofplays, etc.), where such description is in a digitally readable form;and

[0014] a digital signature that ensures the integrity of the license.

[0015] The user should not be able to decrypt and render the encrypteddigital content without obtaining such a license from the licenseserver. The obtained license is stored in a license store in the user'scomputing device.

[0016] Importantly, the license server only issues a license to a DRMsystem that is ‘trusted’ (i.e., that can authenticate itself). Toimplement ‘trust’, the DRM system is equipped with a ‘black box’ thatperforms decryption and encryption functions for such DRM system. Theblack box includes a public/private key pair, a version number and aunique signature, all as provided by an approved certifying authority.The public key is made available to the license server for purposes ofencrypting portions of the issued license, thereby binding such licenseto such black box. The private key is available to the black box only,and not to the user or anyone else, for purposes of decryptinginformation encrypted with the corresponding public key. The DRM systemis initially provided with a black box with a public/private key pair,and the user is prompted to download from a black box server an updatedsecure black box when the user first requests a license. The black boxserver provides the updated black box, along with a uniquepublic/private key pair. Such updated black box is written in uniqueexecutable code that will run only on the user's computing device, andis re-updated on a regular basis.

[0017] When a user requests a license, the client machine sends theblack box public key, version number, and signature to the licenseserver, and such license server issues a license only if the versionnumber is current and the signature is valid. A license request alsoincludes an identification of the digital content for which a license isrequested and a key ID that identifies the decryption key associatedwith the requested digital content. The license server uses the blackbox public key to encrypt the decryption key, and the decryption key toencrypt the license terms, then downloads the encrypted decryption keyand encrypted license terms to the user's computing device along with alicense signature.

[0018] Once the downloaded license has been stored in the DRM systemlicense store, the user can render the digital content according to therights conferred by the license and specified in the license terms. Whena request is made to render the digital content, the black box is causedto decrypt the decryption key and license terms, and a DRM systemlicense evaluator evaluates such license terms. The black box decryptsthe encrypted digital content only if the license evaluation results ina decision that the requester is allowed to play such content. Thedecrypted content is provided to the rendering application forrendering.

[0019] In the present invention, a rendering application on a computingdevice requests a digital rights management (DRM) system on thecomputing device to authorize rendering of digital content based on acorresponding digital license. If unavailable, the DRM system attemptsto silently acquire the license from a license server without theintervention of a user. In the course thereof, the rendering applicationreceives status information from the DRM system relating to theattempted license acquisition by the DRM system and displays thereceived status information in a status display portion of the renderingapplication.

[0020] If the attempt to silently acquire the license fails, therendering application allows a user to attempt to acquire the licensefrom a license server by way of a browser hosted by the renderingapplication. In particular, the rendering application hosts the browser,causes the browser to navigate to a license server, allows a user tocommunicate with the license server by way of the hosted browser toacquire the license, and shuts down the hosted browser upon receivingthe license from the license server.

BRIEF DESCRIPTION OF THE DRAWINGS

[0021] The foregoing summary, as well as the following detaileddescription of the embodiments of the present invention, will be betterunderstood when read in conjunction with the appended drawings. For thepurpose of illustrating the invention, there are shown in the drawingsembodiments which are presently preferred. As should be understood,however, the invention is not limited to the precise arrangements andinstrumentalities shown. In the drawings:

[0022]FIG. 1 is a block diagram showing an enforcement architecture inaccordance with one embodiment of the present invention;

[0023]FIG. 2 is a block diagram of the authoring tool of thearchitecture of FIG. 1 in accordance with one embodiment of the presentinvention;

[0024]FIG. 3 is a block diagram of a digital content package havingdigital content for use in connection with the architecture of FIG. 1 inaccordance with one embodiment of the present invention;

[0025]FIG. 4 is a block diagram of the user's computing device of FIG. 1in accordance with one embodiment of the present invention;

[0026]FIGS. 5A and 5B are flow diagrams showing the steps performed inconnection with the Digital Rights Management (DRM) system of thecomputing device of FIG. 4 to render content in accordance with oneembodiment of the present invention;

[0027]FIG. 6 is a flow diagram showing the steps performed in connectionwith the DRM system of FIG. 4 to determine whether any valid, enablinglicenses are present in accordance with one embodiment of the presentinvention;

[0028]FIG. 7 is a flow diagram showing the steps performed in connectionwith the DRM system of FIG. 4 to obtain a license in accordance with oneembodiment of the present invention;

[0029]FIG. 8 is a block diagram of a digital license for use inconnection with the architecture of FIG. 1 in accordance with oneembodiment of the present invention;

[0030]FIG. 9 is a flow diagram showing the steps performed in connectionwith the DRM system of FIG. 4 to obtain a new black box in accordancewith one embodiment of the present invention;

[0031]FIG. 10 is a flow diagram showing the key transaction stepsperformed in connection with the DRM system of FIG. 4 to validate alicense and a piece of digital content and render the content inaccordance with one embodiment of the present invention;

[0032]FIG. 11 is a block diagram showing the license evaluator of FIG. 4along with a Digital Rights License (DRL) of a license and a languageengine for interpreting the DRL in accordance with one embodiment of thepresent invention;

[0033]FIG. 12 is a block diagram representing a general purpose computersystem in which aspects of the present invention and/or portions thereofmay be incorporated; and

[0034]FIG. 13 is a block diagram showing the rendering application ofFIG. 4 hosting a browser and operating in concert with the DRM system ofFIG. 4 to supervise acquisition of a license from the license server ofFIG. 1 in accordance with one embodiment of the present invention; and

[0035]FIGS. 14A and 14B are flow diagrams showing various stepsperformed in connection with the elements shown in FIG. 13 duringsupervised license acquisition in accordance with one embodiment of thepresent invention.

DETAILED DESCRIPTION OF THE INVENTION

[0036] Referring to the drawings in details, wherein like numerals areused to indicate like elements throughout, there is shown in FIG. 1 anenforcement architecture 10 in accordance with one embodiment of thepresent invention. Overall, the enforcement architecture 10 allows anowner of digital content 12 to specify license rules that must besatisfied before such digital content 12 is allowed to be rendered on auser's computing device 14. Such license rules are embodied within adigital license 16 that the user/user's computing device 14(hereinafter, such terms are interchangeable unless circumstancesrequire otherwise) must obtain from the content owner or an agentthereof. The digital content 12 is distributed in an encrypted form, andmay be distributed freely and widely. Preferably, the decrypting key(KD) for decrypting the digital content 12 is included with the license16.

[0037] Computer Environment

[0038]FIG. 12 and the following discussion are intended to provide abrief general description of a suitable computing environment in whichthe present invention and/or portions thereof may be implemented.Although not required, the invention is described in the general contextof computer-executable instructions, such as program modules, beingexecuted by a computer, such as a client workstation or a server.Generally, program modules include routines, programs, objects,components, data structures and the like that perform particular tasksor implement particular abstract data types. Moreover, it should beappreciated that the invention and/or portions thereof may be practicedwith other computer system configurations, including hand-held devices,multi-processor systems, microprocessor-based or programmable consumerelectronics, network PCs, minicomputers, mainframe computers and thelike. The invention may also be practiced in distributed computingenvironments where tasks are performed by remote processing devices thatare linked through a communications network. In a distributed computingenvironment, program modules may be located in both local and remotememory storage devices.

[0039] As shown in FIG. 12, an exemplary general purpose computingsystem includes a conventional personal computer 120 or the like,including a processing unit 121, a system memory 122, and a system bus123 that couples various system components including the system memoryto the processing unit 121. The system bus 123 may be any of severaltypes of bus structures including a memory bus or memory controller, aperipheral bus, and a local bus using any of a variety of busarchitectures. The system memory includes read-only memory (ROM) 124 andrandom access memory (RAM) 125. A basic input/output system 126 (BIOS),containing the basic routines that help to transfer information betweenelements within the personal computer 120, such as during start-up, isstored in ROM 124.

[0040] The personal computer 120 may further include a hard disk drive127 for reading from and writing to a hard disk (not shown), a magneticdisk drive 128 for reading from or writing to a removable magnetic disk129, and an optical disk drive 130 for reading from or writing to aremovable optical disk 131 such as a CD-ROM or other optical media. Thehard disk drive 127, magnetic disk drive 128, and optical disk drive 130are connected to the system bus 123 by a hard disk drive interface 132,a magnetic disk drive interface 133, and an optical drive interface 134,respectively. The drives and their associated computer-readable mediaprovide non-volatile storage of computer readable instructions, datastructures, program modules and other data for the personal computer 20.

[0041] Although the exemplary environment described herein employs ahard disk, a removable magnetic disk 129, and a removable optical disk131, it should be appreciated that other types of computer readablemedia which can store data that is accessible by a computer may also beused in the exemplary operating environment. Such other types of mediainclude a magnetic cassette, a flash memory card, a digital video disk,a Bernoulli cartridge, a random access memory (RAM), a read-only memory(ROM), and the like.

[0042] A number of program modules may be stored on the hard disk,magnetic disk 129, optical disk 131, ROM 124 or RAM 125, including anoperating system 135, one or more application programs 136, otherprogram modules 137 and program data 138. A user may enter commands andinformation into the personal computer 120 through input devices such asa keyboard 140 and pointing device 142. Other input devices (not shown)may include a microphone, joystick, game pad, satellite disk, scanner,or the like. These and other input devices are often connected to theprocessing unit 121 through a serial port interface 146 that is coupledto the system bus, but may be connected by other interfaces, such as aparallel port, game port, or universal serial bus (USB). A monitor 147or other type of display device is also connected to the system bus 123via an interface, such as a video adapter 148. In addition to themonitor 147, a personal computer typically includes other peripheraloutput devices (not shown), such as speakers and printers. The exemplarysystem of FIG. 12 also includes a host adapter 155, a Small ComputerSystem Interface (SCSI) bus 156, and an external storage device 162connected to the SCSI bus 156.

[0043] The personal computer 120 may operate in a networked environmentusing logical connections to one or more remote computers, such as aremote computer 149. The remote computer 149 may be another personalcomputer, a server, a router, a network PC, a peer device or othercommon network node, and typically includes many or all of the elementsdescribed above relative to the personal computer 120, although only amemory storage device 150 has been illustrated in FIG. 12. The logicalconnections depicted in FIG. 12 include a local area network (LAN) 151and a wide area network (WAN) 152. Such networking environments arecommonplace in offices, enterprise-wide computer networks, intranets,and the Internet.

[0044] When used in a LAN networking environment, the personal computer120 is connected to the LAN 151 through a network interface or adapter153. When used in a WAN networking environment, the personal computer120 typically includes a modem 154 or other means for establishingcommunications over the wide area network 152, such as the Internet. Themodem 154, which may be internal or external, is connected to the systembus 123 via the serial port interface 146. In a networked environment,program modules depicted relative to the personal computer 120, orportions thereof, may be stored in the remote memory storage device. Itwill be appreciated that the network connections shown are exemplary andother means of establishing a communications link between the computersmay be used.

[0045] Architecture

[0046] Referring again to FIG. 1, in one embodiment of the presentinvention, the architecture 10 includes an authoring tool 18, acontent-key database 20, a content server 22, a license server 24, and ablack box server 26, as well as the aforementioned user's computingdevice 14.

[0047] Architecture—Authoring Tool 18

[0048] The authoring tool 18 is employed by a content owner to package apiece of digital content 12 into a form that is amenable for use inconnection with the architecture 10 of the present invention. Inparticular, the content owner provides the authoring tool 18 with thedigital content 12, instructions and/or rules that are to accompany thedigital content 12, and instructions and/or rules as to how the digitalcontent 12 is to be packaged. The authoring tool 18 then produces adigital content package 12 p having the digital content 12 encryptedaccording to an encryption/decryption key, and the instructions and/orrules that accompany the digital content 12.

[0049] In one embodiment of the present invention, the authoring tool 18is instructed to serially produce several different digital content 12packages 12 p, each having the same digital content 12 encryptedaccording to a different encryption/decryption key. As should beunderstood, having several different packages 12 p with the same digitalcontent 12 may be useful for tracking the distribution of such packages12 p/content 12 (hereinafter simply “digital content 12”, unlesscircumstances require otherwise). Such distribution tracking is notordinarily necessary, but may be used by an investigative authority incases where the digital content 12 has been illegally sold or broadcast.

[0050] In one embodiment of the present invention, theencryption/decryption key that encrypts the digital content 12 is asymmetric key, in that the encryption key is also the decryption key(KD). As will be discussed below in more detail, such decryption key(KD) is delivered to a user's computing device 14 in a hidden form aspart of a license 16 for such digital content 12. Preferably, each pieceof digital content 12 is provided with a content ID (or each package 12p is provided with a package ID), each decryption key (KD) has a key ID,and the authoring tool 18 causes the decryption key (KD), key ID, andcontent ID (or package ID) for each piece of digital content 12 (or eachpackage 12 p) to be stored in the content-key database 20. In addition,license data regarding the types of licenses 16 to be issued for thedigital content 12 and the terms and conditions for each type of license16 may be stored in the content-key database 20, or else in anotherdatabase (not shown). Preferably, the license data can be modified bythe content owner at a later time as circumstances and market conditionsmay require.

[0051] In use, the authoring tool 18 is supplied with informationincluding, among other things:

[0052] the digital content 12 to be packaged;

[0053] the type and parameters of watermarking and/or fingerprinting tobe employed, if any;

[0054] the type and parameters of data compression to be employed, ifany;

[0055] the type and parameters of encryption to be employed;

[0056] the type and parameters of serialization to be employed, if any;and

[0057] the instructions and/or rules that are to accompany the digitalcontent 12.

[0058] As is known, a watermark is a hidden, computer-readable signalthat is added to the digital content 12 as an identifier. A fingerprintis a watermark that is different for each instance. As should beunderstood, an instance is a version of the digital content 12 that isunique. Multiple copies of any instance may be made, and any copy is ofa particular instance. When a specific instance of digital content 12 isillegally sold or broadcast, an investigative authority can perhapsidentify suspects according to the watermark/fingerprint added to suchdigital content 12.

[0059] Data compression may be performed according to any appropriatecompression algorithm without departing from the spirit and scope of thepresent invention. For example, the .mp3 or .wav compression algorithmmay be employed. Of course, the digital content 12 may already be in acompressed state, in which case no additional compression is necessary.

[0060] The instructions and/or rules that are to accompany the digitalcontent 12 may include practically any appropriate instructions, rules,or other information without departing from the spirit and scope of thepresent invention. As will be discussed below, such accompanyinginstructions/rules/information are primarily employed by the user andthe user's computing device 14 to obtain a license 16 to render thedigital content 12. Accordingly, such accompanyinginstructions/rules/information may include an appropriately formattedlicense acquisition script or the like, as will be described in moredetail below. In addition, or in the alternative, such accompanyinginstructions/rules/information may include ‘preview’ informationdesigned to provide a user with a preview of the digital content 12.

[0061] With the supplied information, the authoring tool 18 thenproduces one or more packages 12 p corresponding to the digital content12. Each package 12 p may then be stored on the content server 22 fordistribution to the world.

[0062] In one embodiment of the present invention, and referring now toFIG. 2, the authoring tool 18 is a dynamic authoring tool 18 thatreceives input parameters which can be specified and operated on.Accordingly, such authoring tool 18 can rapidly produce multiplevariations of package 12 p for multiple pieces of digital content 12.Preferably, the input parameters are embodied in the form of adictionary 28, as shown, where the dictionary 28 includes suchparameters as:

[0063] the name of the input file 29 a having the digital content 12;

[0064] the type of encoding that is to take place

[0065] the encryption/decryption key (KD) to be employed,

[0066] the accompanying instructions/rules/information (‘headerinformation’) to be packaged with the digital content 12 in the package12 p.

[0067] the type of muxing that is to occur; and

[0068] the name of the output file 29 b to which the package 12 p basedon the digital content 12 is to be written.

[0069] As should be understood, such dictionary 28 is easily and quicklymodifiable by an operator of the authoring tool 18 (human or machine),and therefore the type of authoring performed by the authoring tool 18is likewise easily and quickly modifiable in a dynamic manner. In oneembodiment of the present invention, the authoring tool 18 includes anoperator interface (not shown) displayable on a computer screen to ahuman operator. Accordingly, such operator may modify the dictionary 28by way of the interface, and further may be appropriately aided and/orrestricted in modifying the dictionary 28 by way of the interface.

[0070] In the authoring tool 18, and as seen in FIG. 2, a source filter18 a receives the name of the input file 29 a having the digital content12 from the dictionary 28, and retrieves such digital content 12 fromsuch input file and places the digital content 12 into a memory 29 csuch as a RAM or the like. An encoding filter 18 b then performsencoding on the digital content 12 in the memory 29 c to transfer thefile from the input format to the output format according to the type ofencoding specified in the dictionary 28 (i.e., .wav to asp, .mp3 to.asp, etc.), and places the encoded digital content 12 in the memory 29c. As shown, the digital content 12 to be packaged (music, e.g.) isreceived in a compressed format such as the .wav or .mp3 format, and istransformed into a format such as the .asp (active streaming protocol)format. Of course, other input and output formats may be employedwithout departing from the spirit and scope of the present invention.

[0071] Thereafter, an encryption filter 18 c encrypts the encodeddigital content 12 in the memory 29 c according to theencryption/decryption key (KD) specified in the dictionary 28, andplaces the encrypted digital content 12 in the memory 29 c. A headerfilter 18 d then adds the header information specified in the dictionary28 to the encrypted digital content 12 in the memory 29 c.

[0072] As should be understood, depending on the situation, the package12 p may include multiple streams of temporally aligned digital content12 (one stream being shown in FIG. 2), where such multiple streams aremultiplexed (i.e., ‘muxed’). Accordingly, a mux filter 18 e performsmuxing on the header information and encrypted digital content 12 in thememory 29 c according to the type of muxing specified in the dictionary28, and places the result in the memory 29 c. A file writer filter 18 fthen retrieves the result from the memory 29 c and writes such result tothe output file 29 b specified in the dictionary 28 as the package 12 p.

[0073] It should be noted that in certain circumstances, the type ofencoding to be performed will not normally change. Since the type ofmuxing typically is based on the type of encoding, it is likewise thecase that the type of muxing will not normally change, either. If thisis in fact the case, the dictionary 28 need not include parameters onthe type of encoding and/or the type of muxing. Instead, it is onlynecessary that the type of encoding be ‘hardwired’ into the encodingfilter and/or that the type of muxing be ‘hardwired’ into the muxfilter. Of course, as circumstance require, the authoring tool 18 maynot include all of the aforementioned filters, or may include otherfilters, and any included filter may be hardwired or may perform itsfunction according to parameters specified in the dictionary 28, allwithout departing from the spirit and scope of the present invention.

[0074] Preferably, the authoring tool 18 is implemented on anappropriate computer, processor, or other computing machine by way ofappropriate software. The structure and operation of such machine andsuch software should be apparent based on the disclosure herein andtherefore do not require any detailed discussion in the presentdisclosure.

[0075] Architecture—Content Server 22

[0076] Referring again to FIG. 1, in one embodiment of the presentinvention, the content server 22 distributes or otherwise makesavailable for retrieval the packages 12 p produced by the authoring tool18. Such packages 12 p may be distributed as requested by the contentserver 22 by way of any appropriate distribution channel withoutdeparting from the spirit and scope of the present invention. Forexample, such distribution channel may be the Internet or anothernetwork, an electronic bulletin board, electronic mail, or the like. Inaddition, the content server 22 may be employed to copy the packages 12p onto magnetic or optical disks or other storage devices, and suchstorage devices may then be distributed.

[0077] It will be appreciated that the content server 22 distributespackages 12 p without regard to any trust or security issues. Asdiscussed below, such issues are dealt with in connection with thelicense server 24 and the relationship between such license server 24and the user's computing device 14. In one embodiment of the presentinvention, the content server 22 freely releases and distributespackages 12 p having digital content 12 to any distributee requestingsame. However, the content server 22 may also release and distributesuch packages 12 p in a restricted manner without departing from thespirit and scope of the present invention. For example, the contentserver 22 may first require payment of a pre-determined distribution feeprior to distribution, or may require that a distributes identifyitself, or may indeed make a determination of whether distribution is tooccur based on an identification of the distributee.

[0078] In addition, the content server 22 may be employed to performinventory management by controlling the authoring tool 18 to generate anumber of different packages 12 p in advance to meet an anticipateddemand. For example, the server could generate 100 packages 12 p basedon the same digital content 12, and serve each package 12 p 10 times. Assupplies of packages 12 p dwindle to 20, for example, the content server22 may then direct the authoring tool 18 to generate 80 additionalpackages 12 p, again for example.

[0079] Preferably, the content server 22 in the architecture 10 has aunique public/private key pair (PU-CS, PR-CS) that is employed as partof the process of evaluating a license 16 and obtaining a decryption key(KD) for decrypting corresponding digital content 12, as will beexplained in more detail below. As is known, a public/private key pairis an asymmetric key, in that what is encrypted in one of the keys inthe key pair can only be decrypted by the other of the keys in the keypair. In a public/private key pair encryption system, the public key maybe made known to the world, but the private key should always be held inconfidence by the owner of such private key. Accordingly, if the contentserver 22 encrypts data with its private key (PR-CS), it can send theencrypted data out into the world with its public key (PU-CS) fordecryption purposes. Correspondingly, if an external device wants tosend data to the content server 22 so that only such content server 22can decrypt such data, such external device must first obtain the publickey of the content server 22 (PU-CS) and then must encrypt the data withsuch public key. Accordingly, the content server 22 (and only thecontent server 22) can then employ its private key (PR-CS) to decryptsuch encrypted data.

[0080] As with the authoring tool 18, the content server 22 isimplemented on an appropriate computer, processor, or other computingmachine by way of appropriate software. The structure and operation ofsuch machine and such software should be apparent based on thedisclosure herein and therefore do not require any detailed discussionin the present disclosure. Moreover, in one embodiment of the presentinvention, the authoring tool 18 and the content server 22 may reside ona single computer, processor, or other computing machine, each in aseparate work space. It should be recognized, moreover, that the contentserver 22 may in certain circumstances include the authoring tool 18and/or perform the functions of the authoring tool 18, as discussedabove.

[0081] Structure of Digital Content Package 12 p

[0082] Referring now to FIG. 3, in one embodiment of the presentinvention, the digital content package 12 p as distributed by thecontent server 22 includes:

[0083] the digital content 12 encrypted with the encryption/decryptionkey (KD), as was discussed above (i.e., (KD(CONTENT)));

[0084] the content ID (or package ID) of such digital content 12 (orpackage 12 p);

[0085] the key ID of the decryption key (KD);

[0086] license acquisition information, preferably in an un-encryptedform; and

[0087] the key KD encrypting the content server 22 public key (PU-CS),signed by the content server 22 private key (PR-CS) (i.e., (KD (PU-CS) S(PR-CS))).

[0088] With regard to (KD (PU-CS) S (PR-CS)), it is to be understoodthat such item is to be used in connection with validating the digitalcontent 12 and/or package 12 p, as will be explained below. Unlike acertificate with a digital signature (see below), the key (PU-CS) is notnecessary to get at (KD (PU-CS)). Instead, the key (PU-CS) is obtainedmerely by applying the decryption key (KD). Once so obtained, such key(PU-CS) may be employed to test the validity of the signature (S(PR-CS)).

[0089] It should also be understood that for such package 12 p to beconstructed by the authoring tool 18, such authoring tool 18 mustalready possess the license acquisition information and (KD (PU-CS) S(PR-CS)), presumably as header information supplied by the dictionary28. Moreover, the authoring tool 18 and the content server 22 mustpresumably interact to construct (KD (PU-CS) S (PR-CS)). Suchinteraction may for example include the steps of:

[0090] the content server 22 sending (PU-CS) to the authoring tool 18;

[0091] the authoring tool 18 encrypting (PU-CS) with (KD) to produce (KD(PU-CS));

[0092] the authoring tool 18 sending (KD (PU-CS)) to the content server22;

[0093] the content server 22 signing (KD (PU-CS)) with (PR-CS) toproduce (KD (PU-CS) S (PR-CS)); and

[0094] the content server 22 sending (KD (PU-CS) S (PR-CS)) to theauthoring tool 18.

[0095] Architecture—License Server 24

[0096] Referring again to FIG. 1, in one embodiment of the presentinvention, the license server 24 performs the functions of receiving arequest for a license 16 from a user's computing device 14 in connectionwith a piece of digital content 12, determining whether the user'scomputing device 14 can be trusted to honor an issued license 16,negotiating such a license 16, constructing such license 16, andtransmitting such license 16 to the user's computing device 14.Preferably, such transmitted license 16 includes the decryption key (KD)for decrypting the digital content 12. Such license server 24 and suchfunctions will be explained in more detail below. Preferably, and likethe content server 22, the license server 24 in the architecture 10 hasa unique public/private key pair (PU-LS, PR-LS) that is employed as partof the process of evaluating a license 16 and obtaining a decryption key(KD) for decrypting corresponding digital content 12, as will beexplained in more detail below.

[0097] As with the authoring tool 18 and the content server 22, thelicense server 24 is implemented on an appropriate computer, processor,or other computing machine by way of appropriate software. The structureand operation of such machine and such software should be apparent basedon the disclosure herein and therefore do not require any detaileddiscussion in the present disclosure. Moreover, in one embodiment of thepresent invention the authoring tool 18 and/or the content server 22 mayreside on a single computer, processor, or other computing machinetogether with the license server 24, each in a separate work space.

[0098] In one embodiment of the present invention, prior to issuance ofa license 16, the license server 24 and the content server 22 enter intoan agency agreement or the like, wherein the license server 24 in effectagrees to be the licensing authority for at least a portion of thedigital content 12 distributed by the content server 22. As should beunderstood, one content server 22 may enter into an agency agreement orthe like with several license servers 24, and/or one license server 24may enter into an agency agreement or the like with several contentservers 22, all without departing from the spirit and scope of thepresent invention.

[0099] Preferably, the license server 24 can show to the world that itdoes in fact have the authority to issue a license 16 for digitalcontent 12 distributed by the content server 22. To do so, it ispreferable that the license server 24 send to the content server 22 thelicense server 24 public key (PU-LS), and that the content server 22then send to the license server 24 a digital certificate containingPU-LS as the contents signed by the content server 22 private key (CERT(PU-LS) S (PR-CS)). As should be understood, the contents (PU-LS) insuch certificate can only be accessed with the content server 22 publickey (PU-CS). As should also be understood, in general, a digitalsignature of underlying data is an encrypted form of such data, and willnot match such data when decrypted if such data has been adulterated orotherwise modified.

[0100] As a licensing authority in connection with a piece of digitalcontent 12, and as part of the licensing function, the license server 24must have access to the decryption key (KD) for such digital content 12.Accordingly, it is preferable that license server 24 have access to thecontent-key database 20 that has the decryption key (KD), key ID, andcontent ID (or package ID) for such digital content 12 (or package 12p).

[0101] Architecture—Black Box Server 26

[0102] Still referring to FIG. 1, in one embodiment of the presentinvention, the black box server 26 performs the functions of installingand/or upgrading a new black box 30 in a user's computing device 14. Aswill be explained in more detail below, the black box 30 performsencryption and decryption functions for the user's computing device 14.As will also be explained in more detail below, the black box 30 isintended to be secure and protected from attack. Such security andprotection is provided, at least in part, by upgrading the black box 30to a new version as necessary by way of the black box server 26, as willbe explained in more detail below.

[0103] As with the authoring tool 18, the content server 22, and thelicense server 24, the black box server 26 is implemented on anappropriate computer, processor, or other computing machine by way ofappropriate software. The structure and operation of such machine andsuch software should be apparent based on the disclosure herein andtherefore do not require any detailed discussion in the presentdisclosure. Moreover, in one embodiment of the present invention thelicense server 24, the authoring tool 18, and/or the content server 22may reside on a single computer, processor, or other computing machinetogether with the black box server 26, each in a separate work space.Note, though, that for security purposes, it may be wise to have theblack box server 26 on a separate machine.

[0104] Architecture—User's Computing Device 14

[0105] Referring now to FIG. 4, in one embodiment of the presentinvention, the user's computing device 14 is a personal computer or thelike, having elements including a keyboard, a mouse, a screen, aprocessor, RAM, ROM, a hard drive, a floppy drive, a CD player, and/orthe like. However, the user's computing device 14 may also be adedicated viewing device such as a television or monitor, a dedicatedaudio device such as a stereo or other music player, a dedicatedprinter, or the like, among other things, all without departing from thespirit and scope of the present invention.

[0106] The content owner for a piece of digital content 12 must trustthat the user's computing device 14 will abide by the rules specified bysuch content owner, i.e. that the digital content 12 will not berendered unless the user obtains a license 16 that permits the renderingin the manner sought. Preferably, then, the user's computing device 14must provide a trusted component or mechanism 32 that can satisfy to thecontent owner that such computing device 14 will not render the digitalcontent 12 except according to the license rules embodied in the license16 associated with the digital content 12 and obtained by the user.

[0107] Here, the trusted mechanism 32 is a Digital Rights Management(DRM) system 32 that is enabled when a user requests that a piece ofdigital content 12 be rendered, that determines whether the user has alicense 16 to render the digital content 12 in the manner sought, thateffectuates obtaining such a license 16 if necessary, that determineswhether the user has the right to play the digital content 12 accordingto the license 16, and that decrypts the digital content 12 forrendering purposes if in fact the user has such right according to suchlicense 16. The contents and function of the DRM system 32 on the user'scomputing device 14 and in connection with the architecture 10 aredescribed below.

[0108] DRM System 32

[0109] The DRM system 32 performs four main functions with thearchitecture 10 disclosed herein: (1) content acquisition, (2) licenseacquisition, (3) content rendering, and (4) black box 30installation/update. Preferably, any of the functions can be performedat any time, although it is recognized that some of the functionsalready require that digital content 12 be acquired.

[0110] DRM System 32—Content Acquisition

[0111] Acquisition of digital content 12 by a user and/or the user'scomputing device 14 is typically a relatively straight-forward matterand generally involves placing a file having encrypted digital content12 on the user's computing device 14. Of course, to work with thearchitecture 10 and the DRM system 32 disclosed herein, it is necessarythat the encrypted digital content 12 be in a form that is amenable tosuch architecture 10 and DRM system 32, such as the digital package 12 pas will be described below.

[0112] As should be understood, the digital content 12 may be obtainedin any manner from a content server 22, either directly or indirectly,without departing from the spirit and scope of the present invention.For example, such digital content 12 may be downloaded from a networksuch as the Internet, located on an obtained optical or magnetic disk orthe like, received as part of an E-mail message or the like, ordownloaded from an electronic bulletin board or the like.

[0113] Such digital content 12, once obtained, is preferably stored in amanner such that the obtained digital content 12 is accessible by arendering application 34 (to be described below) running on thecomputing device 14, and by the DRM system 32. For example, the digitalcontent 12 may be placed as a file on a hard drive (not shown) of theuser's computing device 14, or on a network server (not shown)accessible to the computing device 14. In the case where the digitalcontent 12 is obtained on an optical or magnetic disk or the like, itmay only be necessary that such disk be present in an appropriate drive(not shown) coupled to the user's computing device 14.

[0114] In the present invention, it is not envisioned that any specialtools are necessary to acquire digital content 12, either from thecontent server 22 as a direct distribution source or from someintermediary as an indirect distribution source. That is, it ispreferable that digital content 12 be as easily acquired as any otherdata file. However, the DRM system 32 and/or the rendering application34 may include an interface (not shown) designed to assist the user inobtaining digital content 12. For example, the interface may include aweb browser especially designed to search for digital content 12, linksto pre-defined Internet web sites that are known to be sources ofdigital content 12, and the like.

[0115] DRM System 32—Content Rendering, Part 1

[0116] Referring now to FIG. 5A, in one embodiment of the presentinvention, assuming the encrypted digital content 12 has beendistributed to and received by a user and placed by the user on thecomputing device 14 in the form of a stored file, the user will attemptto render the digital content 12 by executing some variation on a rendercommand (step 501). For example, such render command may be embodied asa request to ‘play’ or ‘open’ the digital content 12. In some computingenvironments, such as for example the “MICROSOFT WINDOWS” operatingsystem, distributed by MICROSOFT Corporation of Redmond, Wash., suchplay or open command may be as simple as ‘clicking’ on an iconrepresentative of the digital content 12. Of course, other embodimentsof such render command may be employed without departing from the spiritand scope of the present invention. In general, such render command maybe considered to be executed whenever a user directs that a file havingdigital content 12 be opened, run, executed, and/or the like.

[0117] Importantly, and in addition, such render command may be embodiedas a request to copy the digital content 12 to another form, such as toa printed form, a visual form, an audio form, etc. As should beunderstood, the same digital content 12 may be rendered in one form,such as on a computer screen, and then in another form, such as aprinted document. In the present invention, each type of rendering isperformed only if the user has the right to do so, as will be explainedbelow.

[0118] In one embodiment of the present invention, the digital content12 is in the form of a digital file having a file name ending with anextension, and the computing device 14 can determine based on suchextension to start a particular kind of rendering application 34. Forexample, if the file name extension indicates that the digital content12 is a text file, the rendering application 34 is some form of wordprocessor such as the “MICROSOFT WORD”, distributed by MICROSOFTCorporation of Redmond, Wash. Likewise, if the file name extensionindicates that the digital content 12 is an audio, video, and/ormultimedia file, the rendering application 34 is some form of multimediaplayer, such as “MICROSOFT MEDIA PLAYER”, also distributed by MICROSOFTCorporation of Redmond, Wash.

[0119] Of course, other methods of determining a rendering applicationmay be employed without departing from the spirit and scope of thepresent invention. As but one example, the digital content 12 maycontain meta-data in an un-encrypted form (i.e., the aforementionedheader information), where the meta-data includes information on thetype of rendering application 34 necessary to render such digitalcontent 12.

[0120] Preferably, such rendering application 34 examines the digitalcontent 12 associated with the file name and determines whether suchdigital content 12 is encrypted in a rights-protected form (steps 503,505). If not protected, the digital content 12 may be rendered withoutfurther ado (step 507). If protected, the rendering application 34determines from the encrypted digital content 12 that the DRM system 32is necessary to play such digital content 12. Accordingly, suchrendering application 34 directs the user's computing device 14 to runthe DRM system 32 thereon (step 509). Such rendering application 34 thencalls such DRM system 32 to decrypt the digital content 12 (step 51 1).As will be discussed in more detail below, the DRM system 32 in factdecrypts the digital content 12 only if the user has a valid license 16for such digital content 12 and the right to play the digital content 12according to the license rules in the valid license 16. Preferably, oncethe DRM system 32 has been called by the rendering application 34, suchDRM system 32 assumes control from the rendering application 34, atleast for purposes of determining whether the user has a right to playsuch digital content 12 (step 513).

[0121] DRM System 32 Components

[0122] In one embodiment of the present invention, and referring againto FIG. 4, the DRM system 32 includes a license evaluator 36, the blackbox 30, a license store 38, and a state store 40.

[0123] DRM System 32 Components—License Evaluator 36

[0124] The license evaluator 36 locates one or more licenses 16 thatcorrespond to the requested digital content 12, determines whether suchlicenses 16 are valid, reviews the license rules in such valid licenses16, and determines based on the reviewed license rules whether therequesting user has the right to render the requested digital content 12in the manner sought, among other things. As should be understood, thelicense evaluator 36 is a trusted component in the DRM system 32. In thepresent disclosure, to be ‘trusted’ means that the license server 24 (orany other trusting element) is satisfied that the trusted element willcarry out the wishes of the owner of the digital content 12 according tothe rights description in the license 16, and that a user cannot easilyalter such trusted element for any purpose, nefarious or otherwise.

[0125] The license evaluator 36 has to be trusted in order to ensurethat such license evaluator 36 will in fact evaluate a license 16properly, and to ensure that such license evaluator 36 has not beenadulterated or otherwise modified by a user for the purpose of bypassingactual evaluation of a license 16. Accordingly, the license evaluator 36is run in a protected or shrouded environment such that the user isdenied access to such license evaluator 36. Other protective measuresmay of course be employed in connection with the license evaluator 36without departing from the spirit and scope of the present invention.

[0126] DRM System 32 Components—Black Box 30

[0127] Primarily, and as was discussed above, the black box 30 performsencryption and decryption functions in the DRM system 32. In particular,the black box 30 works in conjunction with the license evaluator 36 todecrypt and encrypt certain information as part of the licenseevaluation function. In addition, once the license evaluator 36determines that a user does in fact have the right to render therequested digital content 12 in the manner sought, the black box 30 isprovided with a decryption key (KD) for such digital content 12, andperforms the function of decrypting such digital content 12 based onsuch decryption key (KD).

[0128] The black box 30 is also a trusted component in the DRM system32. In particular, the license server 24 must trust that the black box30 will perform the decryption function only in accordance with thelicense rules in the license 16, and also trust that such black box 30will not operate should it become adulterated or otherwise modified by auser for the nefarious purpose of bypassing actual evaluation of alicense 16. Accordingly, the black box 30 is also run in a protected orshrouded environment such that the user is denied access to such blackbox 30. Again, other protective measures may be employed in connectionwith the black box 30 without departing from the spirit and scope of thepresent invention. Preferably, and like the content server 22 andlicense server 24, the black box 30 in the DRM system 32 has a uniquepublic/private key pair (PU-BB, PR-BB) that is employed as part of theprocess of evaluating the license 16 and obtaining a decryption key (KD)for decrypting the digital content 12, as will be described in moredetail below.

[0129] DRM System 32 Components—License Store 38

[0130] The license store 38 stores licenses 16 received by the DRMsystem 32 for corresponding digital content 12. The license store 38itself need not be trusted since the license store 38 merely storeslicenses 16, each of which already has trust components built thereinto,as will be described below. In one embodiment of the present invention,the license store 38 is merely a sub-directory of a drive such as a harddisk drive or a network drive. However, the license store 38 may beembodied in any other form without departing from the spirit and scopeof the present invention, so long as such license store 38 performs thefunction of storing licenses 16 in a location relatively convenient tothe DRM system 32.

[0131] DRM System 32 Components—State Store 40

[0132] The state store 40 performs the function of maintaining stateinformation corresponding to licenses 16 presently or formerly in thelicense store 38. Such state information is created by the DRM system 32and stored in the state store 40 as necessary. For example, if aparticular license 16 only allows a pre-determined number of renderingsof a piece of corresponding digital content 12, the state store 40maintains state information on how many renderings have in fact takenplace in connection with such license 16. The state store 40 continuesto maintain state information on licenses 16 that are no longer in thelicense store 38 to avoid the situation where it would otherwise beadvantageous to delete a license 16 from the license store 38 and thenobtain an identical license 16 in an attempt to delete the correspondingstate information from the state store 40.

[0133] The state store 40 also has to be trusted in order to ensure thatthe information stored therein is not reset to a state more favorable toa user. Accordingly, the state store 40 is likewise run in a protectedor shrouded environment such that the user is denied access to suchstate store 40. Once again, other protective measures may of course beemployed in connection with the state store 40 without departing fromthe spirit and scope of the present invention. For example, the statestore 40 may be stored by the DRM system 32 on the computing device 14in an encrypted form.

[0134] DRM System 32—Content Rendering, Part 2

[0135] Referring again to FIG. 5A, and again discussing contentrendering in one embodiment of the present invention, once the DRMsystem 32 has assumed control from the calling rendering application 34,such DRM system 32 then begins the process of determining whether theuser has a right to render the requested digital content 12 in themanner sought. In particular, the DRM system 32 either locates a valid,enabling license 16 in the license store (steps 515, 517) or attempts toacquire a valid, enabling license 16 from the license server 24 (i.e.performs the license acquisition function as discussed below and asshown in FIG. 7).

[0136] As a first step, and referring now to FIG. 6, the licenseevaluator 36 of such DRM system 32 checks the license store 38 for thepresence of one or more received licenses 16 that correspond to thedigital content 12 (step 601). Typically, the license 16 is in the formof a digital file, as will be discussed below, although it will berecognized that the license 16 may also be in other forms withoutdeparting from the spirit and scope of the present invention. Typically,the user will receive the digital content 12 without such license 16,although it will likewise be recognized that the digital content 12 maybe received with a corresponding license 16 without departing from thespirit and scope of the present invention.

[0137] As was discussed above in connection with FIG. 3, each piece ofdigital content 12 is in a package 12 p with a content ID (or packageID) identifying such digital content 12 (or package 12 p), and a key IDidentifying the decryption key (KD) that will decrypt the encrypteddigital content 12. Preferably, the content ID (or package ID) and thekey ID are in an un-encrypted form. Accordingly, and in particular,based on the content ID of the digital content 12, the license evaluator36 looks for any license 16 in the license store 38 that contains anidentification of applicability to such content ID. Note that multiplesuch licenses 16 may be found, especially if the owner of the digitalcontent 12 has specified several different kinds of licenses 16 for suchdigital content 12, and the user has obtained multiple ones of suchlicenses 16. If in fact the license evaluator 36 does not find in thelicense store 38 any license 16 corresponding to the requested digitalcontent 12, the DRM system 32 may then perform the function of licenseacquisition (step 519 of FIG. 5), to be described below.

[0138] Assume now that the DRM system 32 has been requested to render apiece of digital content 12, and one or more licenses 16 correspondingthereto are present in the license store 38. In one embodiment of thepresent invention, then, the license evaluator 36 of the DRM system 32proceeds to determine for each such license 16 whether such license 16itself is valid (steps 603 and 605 of FIG. 6). Preferably, and inparticular, each license 16 includes a digital signature 26 based on thecontent 28 of the license 16. As should be understood, the digitalsignature 26 will not match the license 16 if the content 28 has beenadulterated or otherwise modified. Thus, the license evaluator 36 candetermine based on the digital signature 26 whether the content 28 is inthe form that it was received from the license server 24 (i.e., isvalid). If no valid license 16 is found in the license store 38, the DRMsystem 32 may then perform the license acquisition function describedbelow to obtain such a valid license 16.

[0139] Assuming that one or more valid licenses 16 are found, for eachvalid license 16, the license evaluator 36 of the DRM system 32 nextdetermines whether such valid license 16 gives the user the right torender the corresponding digital content 12 in the manner desired (i.e.,is enabling) (steps 607 and 609). In particular, the license evaluator36 determines whether the requesting user has the right to play therequested digital content 12 based on the rights description in eachlicense 16 and based on what the user is attempting to do with thedigital content 12. For example, such rights description may allow theuser to render the digital content 12 into a sound, but not into adecrypted digital copy.

[0140] As should be understood, the rights description in each license16 specifies whether the user has rights to play the digital content 12based on any of several factors, including who the user is, where theuser is located, what type of computing device 14 the user is using,what rendering application 34 is calling the DRM system 32, the date,the time, etc. In addition, the rights description may limit the license16 to a pre-determined number of plays, or pre-determined play time, forexample. In such case, the DRM system 32 must refer to any stateinformation with regard to the license 16, (i.e., how many times thedigital content 12 has been rendered, the total amount of time thedigital content 12 has been rendered, etc.), where such stateinformation is stored in the state store 40 of the DRM system 32 on theuser's computing device 14.

[0141] Accordingly, the license evaluator 36 of the DRM system 32reviews the rights description of each valid license 16 to determinewhether such valid license 16 confers the rights sought to the user. Indoing so, the license evaluator 36 may have to refer to other data localto the user's computing device 14 to perform a determination of whetherthe user has the rights sought. As seen in FIG. 4, such data may includean identification 42 of the user's computing device (machine) 14 andparticular aspects thereof, an identification 44 of the user andparticular aspects thereof, an identification of the renderingapplication 34 and particular aspects thereof, a system clock 46, andthe like. If no valid license 16 is found that provides the user withthe right to render the digital content 12 in the manner sought, the DRMsystem 32 may then perform the license acquisition function describedbelow to obtain such a license 16, if in fact such a license 16 isobtainable.

[0142] Of course, in some instances the user cannot obtain the right torender the digital content 12 in the manner requested, because thecontent owner of such digital content 12 has in effect directed thatsuch right not be granted. For example, the content owner of suchdigital content 12 may have directed that no license 16 be granted toallow a user to print a text document, or to copy a multimediapresentation into an un-encrypted form. In one embodiment of the presentinvention, the digital content 12 includes data on what rights areavailable upon purchase of a license 16, and types of licenses 16available. However, it will be recognized that the content owner of apiece of digital content 12 may at any time change the rights currentlyavailable for such digital content 12 by changing the licenses 16available for such digital content 12.

[0143] DRM System 32—License Acquisition

[0144] Referring now to FIG. 7, if in fact the license evaluator 36 doesnot find in the license store 38 any valid, enabling license 16corresponding to the requested digital content 12, the DRM system 32 maythen perform the function of license acquisition. As shown in FIG. 3,each piece of digital content 12 is packaged with information in anun-encrypted form regarding how to obtain a license 16 for renderingsuch digital content 12 (i.e., license acquisition information).

[0145] In one embodiment of the present invention, such licenseacquisition information may include (among other things) types oflicenses 16 available, and one or more Internet web sites or other siteinformation at which one or more appropriate license servers 24 may beaccessed, where each such license server 24 is in fact capable ofissuing a license 16 corresponding to the digital content 12. Of course,the license 16 may be obtained in other manners without departing fromthe spirit and scope of the present invention. For example, the license16 may be obtained from a license server 24 at an electronic bulletinboard, or even in person or via regular mail in the form of a file on amagnetic or optical disk or the like.

[0146] Assuming that the location for obtaining a license 16 is in facta license server 24 on a network, the license evaluator 36 thenestablishes a network connection to such license server 24 based on theweb site or other site information, and then sends a request for alicense 16 from such connected license server 24 (steps 701, 703). Inparticular, once the DRM system 32 has contacted the license server 24,such DRM system 32 transmits appropriate license request information 36to such license server 24. In one embodiment of the present invention,such license 16 request information 36 may include:

[0147] the public key of the black box 30 of the DRM system 32 (PU-BB);

[0148] the version number of the black box 30 of the DRM system 32;

[0149] a certificate with a digital signature from a certifyingauthority certifying the black box 30 (where the certificate may in factinclude the aforementioned public key and version number of the blackbox 30);

[0150] the content ID (or package ID) that identifies the digitalcontent 12 (or package 12 p);

[0151] the key ID that identifies the decryption key (KD) for decryptingthe digital content 12;

[0152] the type of license 16 requested (if in fact multiple types areavailable);

[0153] the type of rendering application 34 that requested rendering ofthe digital content 12;

[0154] and/or the like, among other things. Of course, greater or lessoramounts of license 16 request information 36 may be transmitted to thelicense server 24 by the DRM system 32 without departing from the spiritand scope of the present invention. For example, information on the typeof rendering application 34 may not be necessary, while additionalinformation about the user and/or the user's computing device 14 may benecessary.

[0155] Once the license server 24 has received the license 16 requestinformation 36 from the DRM system 32, the license server 24 may thenperform several checks for trust/authentication and for other purposes.In one embodiment of the present invention, such license server 24checks the certificate with the digital signature of the certifyingauthority to determine whether such has been adulterated or otherwisemodified (steps 705, 707). If so, the license server 24 refuses to grantany license 16 based on the request information 36. The license server24 may also maintain a list of known ‘bad’ users and/or user's computingdevices 14, and may refuse to grant any license 16 based on a requestfrom any such bad user and/or bad user's computing device 14 on thelist. Such ‘bad’ list may be compiled in any appropriate manner withoutdeparting from the spirit and scope of the present invention.

[0156] Based on the received request and the information associatedtherewith, and particularly based on the content ID (or package ID) inthe license request information, the license server 24 can interrogatethe content-key database 20 (FIG. 1) and locate a record correspondingto the digital content 12 (or package 12 p) that is the basis of therequest. As was discussed above, such record contains the decryption key(KD), key ID, and content ID for such digital content 12. In addition,such record may contain license data regarding the types of licenses 16to be issued for the digital content 12 and the terms and conditions foreach type of license 16. Alternatively, such record may include apointer, link, or reference to a location having such additionalinformation.

[0157] As mentioned above, multiple types of licenses 16 may beavailable. For example, for a relatively small license fee, a license 16allowing a limited number of renderings may be available. For arelatively greater license fee, a license 16 allowing unlimitedrenderings until an expiration date may be available. For a stillgreater license fee, a license 16 allowing unlimited renderings withoutany expiration date may be available. Practically any type of license 16having any kind of license terms may be devised and issued by thelicense server 24 without departing from the spirit and scope of thepresent invention.

[0158] In one embodiment of the present invention, the request for alicense 16 is accomplished with the aid of a web page or the like astransmitted from the license server 24 to the user's computing device14. Preferably, such web page includes information on all types oflicenses 16 available from the license server 24 for the digital content12 that is the basis of the license 16 request.

[0159] In one embodiment of the present invention, prior to issuing alicense 16, the license server 24 checks the version number of the blackbox 30 to determine whether such black box 30 is relatively current(steps 709, 711). As should be understood, the black box 30 is intendedto be secure and protected from attacks from a user with nefariouspurposes (i.e., to improperly render digital content 12 without alicense 16, or outside the terms of a corresponding license 16).However, it is to be recognized that no system and no software device isin fact totally secure from such an attack.

[0160] As should also be understood, if the black box 30 is relativelycurrent, i.e., has been obtained or updated relatively recently, it isless likely that such black box 30 has been successfully attacked bysuch a nefarious user. Preferably, and as a matter of trust, if thelicense server 24 receives a license request with request information 36including a black box 30 version number that is not relatively current,such license server 24 refuses to issue the requested license 16 untilthe corresponding black box 30 is upgraded to a current version, as willbe described below. Put simply, the license server 24 will not trustsuch black box 30 unless such black box 30 is relatively current.

[0161] In the context of the black box 30 of the present invention, theterm ‘current’ or ‘relatively current’ may have any appropriate meaningwithout departing from the spirit and scope of the present invention,consistent with the function of providing trust in the black box 30based on the age or use thereof. For example, ‘current’ may be definedaccording to age (i.e., less than one month old). As an alternativeexample, ‘current’ may be defined based on a number of times that theblack box 30 has decrypted digital content 12 (i.e., less than 200instances of decryption). Moreover, ‘current’ may be based on policy asset by each license server 24, where one license server 24 may define‘current’ differently from another license server 24, and a licenseserver 24 may further define ‘current’ differently depending on thedigital content 12 for which a license 16 is requested, or depending onthe type of license 16 requested, among other things.

[0162] Assuming that the license server 24 is satisfied from the versionnumber of a black box 30 or other indicia thereof that such black box 30is current, the license server 24 then proceeds to negotiate terms andconditions for the license 16 with the user (step 713). Alternatively,the license server 24 negotiates the license 16 with the user, thensatisfies itself from the version number of the black box 30 that suchblack box 30 is current (i.e., performs step 713, then step 711). Ofcourse, the amount of negotiation varies depending on the type oflicense 16 to be issued, and other factors. For example, if the licenseserver 24 is merely issuing a paid-up unlimited use license 16, verylittle need be negotiated. On the other hand, if the license 16 is to bebased on such items as varying values, sliding scales, break points, andother details, such items and details may need to be worked out betweenthe license server 24 and the user before the license 16 can be issued.

[0163] As should be understood, depending on the circumstances, thelicense negotiation may require that the user provide furtherinformation to the license server 24 (for example, information on theuser, the user's computing device 14, etc.). Importantly, the licensenegotiation may also require that the user and the license server 24determine a mutually acceptable payment instrument (a credit account, adebit account, a mailed check, etc.) and/or payment method (paid-upimmediately, spread over a period of time, etc.), among other things.

[0164] Once all the terms of the license 16 have been negotiated andagreed to by both the license server 24 and user (step 715), a digitallicense 16 is generated by the license server 24 (step 719), where suchgenerated license 16 is based at least in part on the license request,the black box 30 public key (PU-BB), and the decryption key (KD) for thedigital content 12 that is the basis of the request as obtained from thecontent-key database 20. In one embodiment of the present invention, andas seen in FIG. 8, the generated license 16 includes:

[0165] the content ID of the digital content 12 to which the license 16applies;

[0166] a Digital Rights License (DRL) 48 (i.e., the rights descriptionor actual terms and conditions of the license 16 written in apredetermined form that the license evaluator 36 can interrogate),perhaps encrypted with the decryption key (KD) (i.e., KD (DRL));

[0167] the decryption key (KD) for the digital content 12 encrypted withthe black box 30 public key (PU-BB) as receive in the license request(i.e.,(PU-BB (KD));

[0168] a digital signature from the license server 24 (without anyattached certificate) based on (KD (DRL)) and (PU-BB (KD)) and encryptedwith the license server 24 private key (i.e., (S (PR-LS))); and

[0169] the certificate that the license server 24 obtained previouslyfrom the content server 22, such certificate indicating that the licenseserver 24 has the authority from the content server 22 to issue thelicense 16 (i.e., (CERT (PU-LS) S (PR-CS))).

[0170] As should be understood, the aforementioned elements and perhapsothers are packaged into a digital file or some other appropriate form.As should also be understood, if the DRL 48 or (PU-BB (KD)) in thelicense 16 should become adulterated or otherwise modified, the digitalsignature (S (PR-LS)) in the license 16 will not match and thereforewill not validate such license 16. For this reason, the DRL 48 need notnecessarily be in an encrypted form (i.e., (KD(DRL)) as mentionedabove), although such encrypted form may in some instances be desirableand therefore may be employed without departing from the spirit andscope of the present invention.

[0171] Once the digital license 16 has been prepared, such license 16 isthen issued to the requestor (i.e., the DRM system 32 on the user'scomputing device 14) (step 719 of FIG. 7). Preferably, the license 16 istransmitted over the same path through which the request therefor wasmade (i.e., the Internet or another network), although another path maybe employed without departing from the spirit and scope of the presentinvention. Upon receipt, the requesting DRM system 32 preferablyautomatically places the received digital license 16 in the licensestore 38 (step 721).

[0172] It is to be understood that a user's computing device 14 may onoccasion malfunction, and licenses 16 stored in the license store 38 ofthe DRM system 32 on such user's computing device 14 may becomeirretrievably lost. Accordingly, it is preferable that the licenseserver 24 maintain a database 50 of issued licenses 16 (FIG. 1), andthat such license server 24 provide a user with a copy or re-issue(hereinafter ‘re-issue’) of an issued license 16 if the user is in factentitled to such re-issue. In the aforementioned case where licenses 16are irretrievably lost, it is also likely the case that stateinformation stored in the state store 40 and corresponding to suchlicenses 16 is also lost. Such lost state information should be takeninto account when re-issuing a license 16. For example, a fixed numberof renderings license 16 might legitimately be re-issued in a pro-ratedform after a relatively short period of time, and not re-issued at allafter a relatively longer period of time.

[0173] DRM System 32—Installation/Upgrade of Black Box 30

[0174] As was discussed above, as part of the function of acquiring alicense 16, the license server 24 may deny a request for a license 16from a user if the user's computing device 14 has a DRM system 32 with ablack box 30 that is not relatively current, i.e., has a relatively oldversion number. In such case, it is preferable that the black box 30 ofsuch DRM system 32 be upgraded so that the license acquisition functioncan then proceed. Of course, the black box 30 may be upgraded at othertimes without departing from the spirit and scope of the presentinvention.

[0175] Preferably, as part of the process of installing the DRM system32 on a user's computing device 14, a non-unique ‘lite’ version of ablack box 30 is provided. Such ‘lite’ black box 30 is then upgraded to aunique regular version prior to rendering a piece of digital content 12.As should be understood, if each black box 30 in each DRM system 32 isunique, a security breach into one black box 30 cannot easily bereplicated with any other black box 30.

[0176] Referring now to FIG. 9, the DRM system 32 obtains the uniqueblack box 30 by requesting same from a black box server 26 or the like(as was discussed above and as shown in FIG. 1) (step 901). Typically,such request is made by way of the Internet, although other means ofaccess may be employed without departing from the spirit and scope ofthe present invention. For example, the connection to a black box server26 may be a direct connection, either locally or remotely. An upgradefrom one unique non-lite black box 30 to another unique non-lite blackbox 30 may also be requested by the DRM system 32 at any time, such asfor example a time when a license server 24 deems the black box 30 notcurrent, as was discussed above.

[0177] Thereafter, the black box server 26 generates a new unique blackbox 30 (step 903). As seen in FIG. 3, each new black box 30 is providedwith a version number and a certificate with a digital signature from acertifying authority. As was discussed above in connection with thelicense acquisition function, the version number of the black box 30indicates the relative age and/or use thereof. The certificate with thedigital signature from the certifying authority, also discussed above inconnection with the license acquisition function, is a proffer orvouching mechanism from the certifying authority that a license server24 should trust the black box 30. Of course, the license server 24 musttrust the certifying authority to issue such a certificate for a blackbox 30 that is in fact trustworthy. It may be the case, in fact, thatthe license server 24 does not trust a particular certifying authority,and refuses to honor any certificate issued by such certifyingauthority. Trust may not occur, for example, if a particular certifyingauthority is found to be engaging in a pattern of improperly issuingcertificates.

[0178] Preferably, and as was discussed above, the black box server 26includes a new unique public/private key pair (PU-BB, PR-BB) with thenewly generated unique black box 30 (step 903 of FIG. 9). Preferably,the private key for the black box 30 (PR-BB) is accessible only to suchblack box 30, and is hidden from and inaccessible by the remainder ofthe world, including the computing device 14 having the DRM system 32with such black box 30, and the user thereof.

[0179] Most any hiding scheme may be employed without departing from thespirit and scope of the present invention, so long as such hiding schemein fact performs the function of hiding the private key (PR-BB) from theworld. As but one example, the private key (PR-BB) may be split intoseveral sub-components, and each sub-component may be encrypted uniquelyand stored in a different location. In such a situation, it ispreferable that such sub-components are never assembled in full toproduce the entire private key (PR-BB).

[0180] In one embodiment of the present invention, such private key(PR-BB) is encrypted according to code-based encryption techniques. Inparticular, in such embodiment, the actual software code of the blackbox 30 (or other software code) is employed as encrypting key(s).Accordingly, if the code of the black box (or the other software code)becomes adulterated or otherwise modified, for example by a user withnefarious purposes, such private key (PR-BB) cannot be decrypted.

[0181] Although each new black box 30 is delivered with a newpublic/private key pair (PU-BB, PR-BB), such new black box 30 is alsopreferably given access to old public/private key pairs from old blackboxes 30 previously delivered to the DRM system 32 on the user'scomputing device 14 (step 905). Accordingly, the upgraded black box 30can still employ the old key pairs to access older digital content 12and older corresponding licenses 16 that were generated according tosuch old key pairs, as will be discussed in more detail below.

[0182] Preferably, the upgraded black box 30 delivered by the black boxserver 26 is tightly tied to or associated with the user's computingdevice 14. Accordingly, the upgraded black box 30 cannot be operablytransferred among multiple computing devices 14 for nefarious purposesor otherwise. In one embodiment of the present invention, as part of therequest for the black box 30 (step 901) the DRM system 32 provideshardware information unique to such DRM system 32 and/or unique to theuser's computing device 14 to the black box server 26, and the black boxserver 26 generates a black box 30 for the DRM system 32 based in parton such provided hardware information. Such generated upgraded black box30 is then delivered to and installed in the DRM system 32 on the user'scomputing device 14 (steps 907, 909). If the upgraded black box 30 isthen somehow transferred to another computing device 14, the transferredblack box 30 recognizes that it is not intended for such other computingdevice 14, and does not allow any requested rendering to proceed on suchother computing device 14.

[0183] Once the new black box 30 is installed in the DRM system 32, suchDRM system 32 can proceed with a license acquisition function or withany other function.

[0184] DRM System 32—Content Rendering, Part 3

[0185] Referring now to FIG. 5B, and assuming, now, that the licenseevaluator 36 has found at least one valid license 16 and that at leastone of such valid licenses 16 provides the user with the rightsnecessary to render the corresponding digital content 12 in the mannersought (i.e., is enabling), the license evaluator 36 then selects one ofsuch licenses 16 for further use (step 519). Specifically, to render therequested digital content 12, the license evaluator 36 and the black box30 in combination obtain the decryption key (KD) from such license 16,and the black box 30 employs such decryption key (KD) to decrypt thedigital content 12. In one embodiment of the present invention, and aswas discussed above, the decryption key (KD) as obtained from thelicense 16 is encrypted with the black box 30 public key (PU-BB(KD)),and the black box 30 decrypts such encrypted decryption key with itsprivate key (PR-BB) to produce the decryption key (KD) (steps 521, 523).However, other methods of obtaining the decryption key (KD) for thedigital content 12 may be employed without departing from the spirit andscope of the present invention.

[0186] Once the black box 30 has the decryption key (KD) for the digitalcontent 12 and permission from the license evaluator 36 to render thedigital content 12, control may be returned to the rendering application34 (steps 525, 527). In one embodiment of the present invention, therendering application 34 then calls the DRM system 32/black box 30 anddirects at least a portion of the encrypted digital content 12 to theblack box 30 for decryption according to the decryption key (KD) (step529). The black box 30 decrypts the digital content 12 based upon thedecryption key (KD) for the digital content 12, and then the black box30 returns the decrypted digital content 12 to the rendering application34 for actual rendering (steps 533, 535). The rendering application 34may either send a portion of the encrypted digital content 12 or theentire digital content 12 to the black box 30 for decryption based onthe decryption key (KD) for such digital content 12 without departingfrom the spirit and scope of the present invention.

[0187] Preferably, when the rendering application 34 sends digitalcontent 12 to the black box 30 for decryption, the black box 30 and/orthe DRM system 32 authenticates such rendering application 34 to ensurethat it is in fact the same rendering application 34 that initiallyrequested the DRM system 32 to run (step 531). Otherwise, the potentialexists that rendering approval may be obtained improperly by basing therendering request on one type of rendering application 34 and in factrendering with another type of rendering application 34. Assuming theauthentication is successful and the digital content 12 is decrypted bythe black box 30, the rendering application 34 may then render thedecrypted digital content 12 (steps 533, 535).

[0188] Sequence of Key Transactions

[0189] Referring now to FIG. 10, in one embodiment of the presentinvention, a sequence of key transactions is performed to obtain thedecryption key (KD) and evaluate a license 16 for a requested piece ofdigital content 12 (i.e., to perform steps 515-523 of FIGS. 5A and 5B).Mainly, in such sequence, the DRM system 32 obtains the decryption key(KD) from the license 16, uses information obtained from the license 16and the digital content 12 to authenticate or ensure the validity ofboth, and then determines whether the license 16 in fact provides theright to render the digital content 12 in the manner sought. If so, thedigital content 12 may be rendered.

[0190] Bearing in mind that each license 16 for the digital content 12,as seen in FIG. 8, includes:

[0191] the content ID of the digital content 12 to which the license 16applies;

[0192] the Digital Rights License (DRL) 48, perhaps encrypted with thedecryption key (KD) (i.e., KD (DRL));

[0193] the decryption key (KD) for the digital content 12 encrypted withthe black box 30 public key (PU-BB) (i.e., (PU-BB (KD));

[0194] the digital signature from the license server 24 based on (KD(DRL)) and (PU-BB (KD)) and encrypted with the license server 24 privatekey (i.e., (S (PR-LS))); and

[0195] the certificate that the license server 24 obtained previouslyfrom the content server 22 (i.e., (CERT (PU-LS) S (PR-CS))), and alsobearing in mind that the package 12 p having the digital content 12, asseen in FIG. 3, includes:

[0196] the content ID of such digital content 12;

[0197] the digital content 12 encrypted by KD (i.e., (KD(CONTENT)));

[0198] a license acquisition script that is not encrypted; and

[0199] the key KD encrypting the content server 22 public key (PU-CS),signed by the content server 22 private key (PR-CS) (i.e., (KD (PU-CS) S(PR-CS))),

[0200] in one embodiment of the present invention, the specific sequenceof key transactions that are performed with regard to a specific one ofthe licenses 16 for the digital content 12 is as follows:

[0201] 1. Based on (PU-BB (KD)) from the license 16, the black box 30 ofthe DRM system 32 on the user's computing device 14 applies its privatekey (PR-BB) to obtain (KD) (step 1001). (PR-BB (PU-BB (KD))=(KD)). Note,importantly, that the black box 30 could then proceed to employ KD todecrypt the digital content 12 without any further ado. However, andalso importantly, the license server 24 trusts the black box 30 not todo so. Such trust was established at the time such license server 24issued the license 16 based on the certificate from the certifyingauthority vouching for the trustworthiness of such black box 30.Accordingly, despite the black box 30 obtaining the decryption key (KD)as an initial step rather than a final step, the DRM system 32 continuesto perform all license 16 validation and evaluation functions, asdescribed below.

[0202] 2. Based on (KD (PU-CS) S (PR-CS)) from the digital content 12,the black box 30 applies the newly obtained decryption key (KD) toobtain (PU-CS) (step 1003). (KD (KD (PU-CS))=(PU-CS)). Additionally, theblack box can apply (PU-CS) as against the signature (S (PR-CS)) tosatisfy itself that such signature and such digital content 12/package12 p is valid (step 1005). If not valid, the process is halted andaccess to the digital content 12 is denied.

[0203] 3. Based on (CERT (PU-LS) S (PR-CS)) from the license 16, theblack box 30 applies the newly obtained content server 22 public key(PU-CS) to satisfy itself that the certificate is valid (step 1007),signifying that the license server 24 that issued the license 16 had theauthority from the content server 22 to do so, and then examines thecertificate contents to obtain (PU-LS) (step 1009). If not valid, theprocess is halted and access to the digital content 12 based on thelicense 16 is denied.

[0204] 4. Based on (S (PR-LS)) from the license 16, the black box 30applies the newly obtained license server 24 public key (PU-LS) tosatisfy itself that the license 16 is valid (step 1011). If not valid,the process is halted and access to the digital content 12 based on thelicense 16 is denied.

[0205] 5. Assuming all validation steps are successful, and that the DRL48 in the license 16 is in fact encrypted with the decryption key (KD),the license evaluator 36 then applies the already-obtained decryptionkey (KD) to (KD(DRL)) as obtained from the license 16 to obtain thelicense terms from the license 16 (i.e., the DRL 48) (step 1013). Ofcourse, if the DRL 48 in the license 16 is not in fact encrypted withthe decryption key (KD), step 1013 may be omitted. The license evaluator36 then evaluates/interrogates the DRL 48 and determines whether theuser's computing device 14 has the right based on the DRL 48 in thelicense 16 to render the corresponding digital content 12 in the mannersought (i.e., whether the DRL 48 is enabling) (step 1015). If thelicense evaluator 36 determines that such right does not exist, theprocess is halted and access to the digital content 12 based on thelicense 16 is denied.

[0206] 6. Finally, assuming evaluation of the license 16 results in apositive determination that the user's computing device 14 has the rightbased on the DRL 48 terms to render the corresponding digital content 12in the manner sought, the license evaluator 36 informs the black box 30that such black box 30 can render the corresponding digital content 12according to the decryption key (KD). The black box 30 thereafterapplies the decryption key (KD) to decrypt the digital content 12 fromthe package 12 p (i.e., (KD(KD(CONTENT))=(CONTENT)) (step 1017).

[0207] It is important to note that the above-specified series of stepsrepresents an alternating or ‘ping-ponging’ between the license 16 andthe digital content 12. Such ping-ponging ensures that the digitalcontent 12 is tightly bound to the license 16, in that the validationand evaluation process can only occur if both the digital content 12 andlicense 16 are present in a properly issued and valid form. In addition,since the same decryption key (KD) is needed to get the content server22 public key (PU-CS) from the license 16 and the digital content 12from the package 12 p in a decrypted form (and perhaps the license terms(DRL 48) from the license 16 in a decrypted form), such items are alsotightly bound. Signature validation also ensures that the digitalcontent 12 and the license 16 are in the same form as issued from thecontent server 22 and the license server 24, respectively. Accordingly,it is difficult if not impossible to decrypt the digital content 12 bybypassing the license server 24, and also difficult if not impossible toalter and then decrypt the digital content 12 or the license 16.

[0208] In one embodiment of the present invention, signatureverification, and especially signature verification of the license 16,is alternately performed as follows. Rather than having a signatureencrypted by the private key of the license server 16 (PR-LS), as isseen in FIG. 8, each license 16 has a signature encrypted by a privateroot key (PR-R) (not shown), where the black box 30 of each DRM system32 includes a public root key (PU-R) (also not shown) corresponding tothe private root key (PR-R). The private root key (PR-R) is known onlyto a root entity, and a license server 24 can only issue licenses 16 ifsuch license server 24 has arranged with the root entity to issuelicenses 16.

[0209] In particular, in such embodiment:

[0210] 1. the license server 24 provides its public key (PU-LS) to theroot entity;

[0211] 2. the root entity returns the license server public key (PU-LS)to such license server 24 encrypted with the private root key (PR-R)(i.e., (CERT (PU-LS) S (PR-R))); and

[0212] 3. the license server 24 then issues a license 16 with asignature encrypted with the license server private key (S (PR-LS)), andalso attaches to the license the certificate from the root entity (CERT(PU-LS) S (PR-R)).

[0213] For a DRM system 18 to validate such issued license 16, then, theDRM system 18:

[0214] 1. applies the public root key (PU-R) to the attached certificate(CERT (PU-LS) S (PR-R)) to obtain the license server public key (PU-LS);and

[0215] 2. applies the obtained license server public key (PU-LS) to thesignature of the license 16 (S (PR-LS).

[0216] Importantly, it should be recognized that just as the root entitygave the license server 24 permission to issue licenses 16 by providingthe certificate (CERT (PU-LS) S (PR-R)) to such license server 24, suchlicense server 24 can provide a similar certificate to a second licenseserver 24 (i.e., (CERT (PU-LS2) S (PR-LS1)), thereby allowing the secondlicense server to also issue licenses 16. As should now be evident, alicense 16 issued by the second license server would include a firstcertificate (CERT (PU-LS1) S (PR-R)) and a second certificate (CERT(PU-LS2) S (PR-LS1)). Likewise, such license 16 is validated byfollowing the chain through the first and second certificates. Ofcourse, additional links in the chain may be added and traversed.

[0217] One advantage of the aforementioned signature verificationprocess is that the root entity may periodically change the private rootkey (PR-R), thereby likewise periodically requiring each license server24 to obtain a new certificate (CERT (PU-LS) S (PR-R)). Importantly, asa requirement for obtaining such new certificate, each license servermay be required to upgrade itself. As with the black box 30, if alicense server 24 is relatively current, i.e., has been upgradedrelatively recently, it is less likely that license server 24 has beensuccessfully attacked. Accordingly, as a matter of trust, each licenseserver 24 is preferably required to be upgraded periodically via anappropriate upgrade trigger mechanism such as the signature verificationprocess. Of course, other upgrade mechanisms may be employed withoutdeparting from the spirit and scope of the present invention.

[0218] Of course, if the private root key (PR-R) is changed, then thepublic root key (PU-R) in each DRM system 18 must also be changed. Suchchange may for example take place during a normal black box 30 upgrade,or in fact may require that a black box 30 upgrade take place. Althougha changed public root key (PU-R) may potentially interfere withsignature validation for an older license 16 issued based on an olderprivate root key (PR-R), such interference may be minimized by requiringthat an upgraded black box 30 remember all old public root keys (PU-R).Alternatively, such interference may be minimized by requiring signatureverification for a license 16 only once, for example the first time suchlicense 16 is evaluated by the license evaluator 36 of a DRM system 18.In such case, state information on whether signature verification hastaken place should be compiled, and such state information should bestored in the state store 40 of the DRM system 18.

[0219] Digital Rights License 48

[0220] In one embodiment of the present invention, the license evaluator36 evaluates a Digital Rights License (DRL) 48 as the rights descriptionor terms of a license 16 to determine if such DRL 48 allows rendering ofa corresponding piece of digital content 12 in the manner sought. In oneembodiment of the present invention, the DRL 48 may be written by alicensor (i.e., the content owner) in any DRL language.

[0221] As should be understood, there are a multitude of ways to specifya DRL 48. Accordingly, a high degree of flexibility must be allowed forin any DRL language. However, it is impractical to specify all aspectsof a DRL 48 in a particular license language, and it is highly unlikelythat the author of such a language can appreciate all possible licensingaspects that a particular digital licensor may desire. Moreover, ahighly sophisticated license language may be unnecessary and even ahindrance for a licensor providing a relatively simple DRL 48.Nevertheless, a licensor should not be unnecessarily restricted in howto specify a DRL 48. At the same time, the license evaluator 36 shouldalways be able to get answers from a DRL 48 regarding a number ofspecific license questions.

[0222] In the present invention, and referring now to FIG. 11, a DRL 48can be specified in any license language, but includes a languageidentifier or tag 54. The license evaluator 36 evaluating the license16, then, performs the preliminary step of reviewing the language tag 54to identify such language, and then selects an appropriate licenselanguage engine 52 for accessing the license 16 in such identifiedlanguage. As should be understood, such license language engine 52 mustbe present and accessible to the license evaluator 36. If not present,the language tag 54 and/or the DRL 48 preferably includes a location 56(typically a web site) for obtaining such language engine 52.

[0223] Typically, the language engine 52 is in the form of an executablefile or set of files that reside in a memory of the user's computingdevice 14, such as a hard drive. The language engine 52 assists thelicense evaluator 36 to directly interrogate the DRL 48, the licenseevaluator 36 interrogates the DRL 48 indirectly via the language engine48 acting as an intermediary, or the like. When executed, the languageengine 52 runs in a work space in a memory of the user's computingdevice 14, such as RAM. However, any other form of language engine 52may be employed without departing from the spirit and scope of thepresent invention.

[0224] Preferably, any language engine 52 and any DRL language supportsat least a number of specific license questions that the licenseevaluator 36 expects to be answered by any DRL 48, as will be discussedbelow. Accordingly, the license evaluator 36 is not tied to anyparticular DRL language; a DRL 48 may be written in any appropriate DRLlanguage; and a DRL 48 specified in a new license language can beemployed by an existing license evaluator 36 by having such licenseevaluator 36 obtain a corresponding new language engine 52.

[0225] DRL Languages

[0226] Two examples of DRL languages, as embodied in respective DRLs 48,are provided below. The first, ‘simple’ DRL 48 is written in a DRLlanguage that specifies license attributes, while the second ‘script’DRL 48 is written in a DRL language that can perform functions accordingto the script specified in the DRL 48. While written in a DRL language,the meaning of each line of code should be apparent based on thelinguistics thereof and/or on the attribute description chart thatfollows: Simple DRL 48: <LICENSE> <DATA> <NAME>Beastie Boy's Play</NAME><ID>39384</ID> <DESCRIPTION>Play the song 3 times</DESCRIPTION><TERMS></TERMS> <VALIDITY> <NOTBEFORE>19980102 23:20:14Z</NOTBEFORE><NOTAFTER>19980102 23:20:14Z</NOTAFTER> <VALIDITY> <ISSUEDDATE>1998010223:20:14Z</ISSUEDDATE> <LICENSORSITE>http://www.foo.com</LICENSORSITE><CONTENT> <NAME>Beastie Boy's</NAME> <ID>392</ID> <KEYID>39292</KEYID><TYPE>MS Encrypted ASF 2.0</TTYPE> </CONTENT> <OWNER><ID>939KDKD393KD</ID> <NAME>Universal</NAME> <PUBLICKEY></PUBLICKEY></OWNER> <LICENSEE> <NAME>Arnold</NAME> <ID>939KDKD393KD</ID><PUBLICKEY></PUBLICKEY> </LICENSEE> <PRINCIPAL TYPE==AND=> <PRINCIPALTYPE==OR=> <PRINCIPAL> <TYPE>x86Computer</TYPE><ID>3939292939d9e939</ID> <NAME>Personal Computer</NAME> <AUTHTYPE>IntelAuthenticated Boot PC SHA-1 DSA512</AUTHTYPE> <AUTH DATA>29293939</AUTHDATA> </PRINCIPAL> <PRINCIPAL> <TYPE>Application</TYPE><ID>2939495939292</ID> <NAME>Windows=s Media Player</NAME><AUTHTYPE>Authenticode SHA-1</AUTHTYPE> <AUTHDATA>93939</AUTHDATA></PRINCIPAL> </PRINCIPAL> <PRINCIPAL> <TYPE>Person</TYPE><ID>39299482010</ID> <NAME>Arnold Blinn</NAME> <AUTHTYPE>Authenticateuser</AUTHTYPE> <AUTH DATA>\\redmond\arnoldb</AUTH DATA> </PRINCIPAL></PRINCIPAL> <DRLTYPE>Simple</DRLTYPE>[the language tag 54] <DRLDATA><START>19980102 23:20:14Z</START> <END>19980102 23:20:14Z</END><COUNT>3</COUNT> <ACTION>PLAY</ACTION> </DRLDATA><ENABLINGBITS>aaaabbbbccccdddd</ENABLINGBITS> </DATA> <SIGNATURE><SIGNERNAME>Universal</SIGNERNAME> <SIGNERID>9382ABK3939DKD</SIGNERID><HASHALGORITHMID>MD5</HASHALGORITHMID> <SIGNALGORITHMID>RSA128</SIGNALGORITHMID> <SIGNATURE>xxxyyyxxxyyyxxxyyy</SIGNATURE><SIGNERPUBLICKEY></SIGNERPUBLICKEY> <CONTENTSIGNEDSIGNERPUBLICKEY></CONTENTSIGNEDSIGNERPUBLICKEY> <SIGNATURE> </LICENSE> Script DRL 48:<LICENSE> <DATA> <NAME>Beastie Boy's Play</NAME> <ID>39384</ID><DESCRIPTION>Play the song unlimited</DESCRIPTION> <TERMS></TERMS><VALIDITY> <NOTBEFORE>19980102 23:20:14Z</NOTBEFORE> <NOTAFTER>1998010223:20:14Z</NOTAFTER> </VALIDITY> <ISSUEDDATE>1998010223:20:14Z</ISSUEDDATE> <LICENSORSITE>http://www.foo.com</LICENSORSITE><CONTENT> <NAME>Beastie Boy's</NAME <ID>392</ID> <KEYID>39292</KEYID><TYPE>MS Encrypted ASF 2.0</TTYPE> </CONTENT> <OWNER><ID>939KDKD393KD</ID> <NAME>Universal</NAME> <PUBLICKEY></PUBLICKEY></OWNER> <LICENSEE> <NAME>Arnold</NAME> <ID>939KDKD393KD</ID><PUBLICKEY></PUBLICKEY> </LICENSEE> <DRLTYPE>Script</DRLTYPE> [thelanguage tag 54] <DRLDATA> function on_enable(action, args) as booleanresult = False if action = “PLAY” then result = True end if on_action =False end function . . . </DRLDATA> </DATA> <SIGNATURE><SIGNERNAME>Universal</SIGNERNAME> <SIGNERID>9382</SIGNERID><SIGNERPUBLICKEY></SIGNERPUBLICKEY> <HASHID>MD5</HASHID> <SIGNID>RSA128</SIGNID> <SIGNATURE>xxxyyyxxxyyyxxxyyy</SIGNATURE><CONTENTSIGNEDSIGNERPUBLICKEY> </CONTENTSIGNEDSIGNERPUBLICKEY></SIGNATURE> </LICENSE>

[0227] In the two DRLs 48 specified above, the attributes listed havethe following descriptions and data types: Attribute Description DataType Id ID of the license GUID Name Name of the license String ContentId ID of the content GUID Content Key Id ID for the encryption key ofthe GUID content Content Name Name of the content String Content TypeType of the content String Owner Id ID of the owner of the content GUIDOwner Name Name of the owner of the content String Owner Public KeyPublic key for owner of content. String This is a base-64 encoded publickey for the owner of the content. Licensee Id Id of the person gettinglicense. It GUID may be null. Licensee Name Name of the person gettinglicense. String It may be null. Licensee Public Key Public key of thelicensee. This is String the base-64 encoded public key of the licensee.It may be null. Description Simple human readable description String ofthe license Terms Legal terms of the license. This String may be apointer to a web page containing legal prose. Validity Not AfterValidity period of license expiration Date Validity Not Before Validityperiod of license start Date Issued Date Date the license was issuedDate DRL Type Type of the DRL. Example include String “SIMPLE” or“SCRIPT” DRL Data Data specific to the DRL String Enabling Bits Theseare the bits that enable String access to the actual content. Theinterpretation of these bits is up to the application, but typicallythis will be the private key for decryption of the content. This datawill be base- 64 encoded. Note that these bits are encrypted using thepublic key of the individual machine. Signer Id ID of person signinglicense GUID Signer Name Name of person signing license String SignerPublic Key Public key for person signing String license. This is thebase-64 encode public key for the signer. Content Signed Signer Publickey for person signing the String Public Key license that has beensigned by the content server private key. The public key to verify thissignature will be encrypted in the content. This is base-64 encoded.Hash Alg Id Algorithm used to generate hash. String This is a string,such as “MD5”. Signature Alg Id Algorithm used to generate Stringsignature. This is a string, such as “RSA 128”. Signature Signature ofthe data. This is base- String 64 encoded data.

[0228] Methods

[0229] As was discussed above, it is preferable that any language engine52 and any DRL language support at least a number of specific licensequestions that the digital license evaluator 36 expects to be answeredby any DRL 48. Recognizing such supported questions may include anyquestions without departing from the spirit and scope of the presentinvention, and consistent with the terminology employed in the two DRL48 examples above, in one embodiment of the present invention, suchsupported questions or ‘methods’ include ‘access methods’, ‘DRLmethods’, and ‘enabling use methods’, as follows:

[0230] Access Methods

[0231] Access methods are used to query a DRL 48 for top-levelattributes.

[0232] VARIANT QueryAttribute (BSTR key)

[0233] Valid keys include License.Name, License.Id, Content.Name,Content.Id, Content.Type, Owner.Name, Owner.Id, Owner.PublicKey,Licensee.Name, Licensee.Id, Licensee.PublicKey, Description, and Terms,each returning a BSTR variant; and Issued, Validity.Start andValidity.End, each returning a Date Variant.

[0234] DRL Methods

[0235] The implementation of the following DRL methods varies from DRL48 to DRL 48. Many of the DRL methods contain a variant parameterlabeled ‘data’ which is intended for communicating more advancedinformation with a DRL 48. It is present largely for futureexpandability.

[0236] Boolean IsActivated(Variant data)

[0237] This method returns a Boolean indicating whether the DRL48/license 16 is activated. An example of an activated license 16 is alimited operation license 16 that upon first play is active for only 48hours.

[0238] Activate(Variant data)

[0239] This method is used to activate a license 16. Once a license 16is activated, it cannot be deactivated.

[0240] Variant QueryDRL(Variant data)

[0241] This method is used to communicate with a more advanced DRL 48.It is largely about future expandability of the DRL 48 feature set.

[0242] Variant GetExpires(BSTR action, Variant data)

[0243] This method returns the expiration date of a license 16 withregard to the passed-in action. If the return value is NULL, the license16 is assumed to never expire or does not yet have an expiration datebecause it hasn't been activated, or the like.

[0244] Variant GetCount(BSTR action, Variant data)

[0245] This method returns the number of operations of the passed-inaction that are left. If NULL is returned, the operation can beperformed an unlimited number of times.

[0246] Boolean IsEnabled(BSTR action, Variant data)

[0247] This method indicates whether the license 16 supports therequested action at the present time.

[0248] Boolean IsSunk(BSTR action, Variant data)

[0249] This method indicates whether the license 16 has been paid for. Alicense 16 that is paid for up front would return TRUE, while a license16 that is not paid for up front, such as a license 16 that collectspayments as it is used, would return FALSE.

[0250] Enabling Use Methods

[0251] These methods are employed to enable a license 16 for use indecrypting content.

[0252] Boolean Validate (BSTR key)

[0253] This method is used to validate a license 16. The passed-in keyis the black box 30 public key (PU-BB) encrypted by the decryption key(KD) for the corresponding digital content 12 (i.e.,( KD(PU-BB))) foruse in validation of the signature of the license 16. A return value ofTRUE indicates that the license 16 is valid. A return value of FALSEindicates invalid.

[0254] int OpenLicense 16(BSTR action, BSTR key, Variant data)

[0255] This method is used to get ready to access the decrypted enablingbits. The passed-in key is (KD(PU-BB)) as described above. A returnvalue of 0 indicates success. Other return values can be defined.

[0256] BSTR GetDecryptedEnablingBits (BSTR action, Variant data)

[0257] Variant GetDecryptedEnablingBitsAsBinary (BSTR action, VariantData)

[0258] These methods are used to access the enabling bits in decryptedform. If this is not successful for any of a number of reasons, a nullstring or null variant is returned.

[0259] void CloseLicense (BSTR action, Variant data)

[0260] This method is used to unlock access to the enabling bits forperforming the passed-in action. If this is not successful for any of anumber of reasons, a null string is returned.

[0261] Heuristics

[0262] As was discussed above, if multiple licenses 16 are present forthe same piece of digital content 12, one of the licenses 16 must bechosen for further use. Using the above methods, the followingheuristics could be implemented to make such choice. In particular, toperform an action (say ‘PLAY’) on a piece of digital content 12, thefollowing steps could be performed:

[0263] 1. Get all licenses 16 that apply to the particular piece ofdigital content 12.

[0264] 2. Eliminate each license 16 that does not enable the action bycalling the IsEnabled function on such license 16.

[0265] 3. Eliminate each license 16 that is not active by callingIsActivated on such license 16.

[0266] 4. Eliminate each license 16 that is not paid for up front bycalling IsSunk on such license 16.

[0267] 5. If any license 16 is left, use it. Use anunlimited-number-of-plays license 16 before using alimited-number-of-plays license 16, especially if theunlimited-number-of-plays license 16 has an expiration date. At anytime, the user should be allowed to select a specific license 16 thathas already been acquired, even if the choice is not cost-effective.Accordingly, the user can select a license 16 based on criteria that areperhaps not apparent to the DRM system 32.

[0268] 6. If there are no licenses 16 left, return status so indicating.The user would then be given the option of:

[0269] using a license 16 that is not paid for up front, if available;

[0270] activating a license 16, if available; and/or

[0271] performing license acquisition from a license server 24.

[0272] Supervised License Acquisition

[0273] As was discussed above in connection with FIG. 7, in the courseof attempting to render a piece of digital content 12, if in fact thelicense evaluator 36 does not find in the license store 38 any valid,enabling corresponding digital license 16, the DRM system 32 may theninitiate the function of license acquisition from a location identifiedin the content package 12 p, where the location may be an Internet website or other site at which a license server 24 may be accessed. As alsodiscussed, acquisition of the license 16 may be accomplishedinteractively between a user and the license server 24 with the aid ofone or more web pages or the like as transmitted from the license server24 to the user's computing device 14.

[0274] In one typical mode of operation, the license acquisition processis initiated in the course of the user employing the renderingapplication 34 (FIG. 4) in an attempt to render the content 12. At leastin the case where the computing device 14 includes a view screen or thelike, indicia of the rendering application 34 is presumably in view onsuch view screen, while indicia of the DRM system 32 is presumably notin view on such view screen. Preferably, the rendering application 34supervises and controls the license acquisition process and inparticular presents the license acquisition process to the user withinthe context of the rendering application 34. Thus, the user is notconfused or upset at the sudden appearance of a web page in a browser.Instead, the user is presented with an overall seamless user experience.

[0275] In one embodiment of the present invention, then, and referringnow to FIG. 13, in the course of acquiring the license 16 and in thecourse of interaction between the user and the license server 24 by wayof web pages, such web pages are viewed on the view screen 60 in abrowser 62 initiated by the rendering application 34, under the controlof such rendering application 34, and viewed within the context of therendering application 34. That is, such web pages are viewed in abrowser 62 hosted by the rendering application 34. Accordingly, thehosting rendering application 34 can control the browser 62 and be madeaware of the actions performed in connection with the browser 62. Inaddition, and significantly, presenting the browser 62 to the userwithin the context of the hosting rendering application 34 is lessjarring to the user, especially when the license acquisition process isautomated and the user may not have been expecting to see the browser62.

[0276] In particular, and referring now to FIGS. 14A and 14B, uponattempting to render the content 12, the rendering application 34detects the protected and encrypted nature of the content 12 (step 1401)and therefore requests the DRM system 32 to authorize the rendering ofthe content 12 and decrypt the content 12 according to the content key(KD) thereof (step 1403). Accordingly, the DRM system 32 searches in thelicense store 38 for a valid and enabling license 16 (step 1405). Ifsuch a license 16 is found, the rendering of the content 12 by therendering application 34 proceeds based on the found license 16 in themanner discussed above (steps 1407,1409). However, if such a license 16is not found, the DRM system 32 so notifies the rendering application 34(steps 1407, 1411) and provides the rendering application 34 withinformation necessary to acquire the necessary license such as thatwhich was described above (a web site identifier identifying a licenseserver 24, a key ID, etc.) (step 1413). Thereafter, the renderingapplication 34 hosts a browser 62 (step 1415), causes the browser 62 tonavigate to the license server 24 (step 1417), and allows the user tocommunicate with the license server 24 by way of the hosted browser 62to obtain the license 16 (step 1419).

[0277] The browser 62 may be any appropriate browser without departingfrom the spirit and scope of the present invention. For example, thebrowser 62 may be a commercial browser such as the MICROSOFT INTERNETEXPLORER browser as manufactured and/or distributed by MICROSOFTCorporation of Redmond, Wash., or may be a specialized browser. Furtherthe browser may have unlimited functionality, or may be endowed withonly those functions necessary for the purpose of fosteringcommunication between the user and the license server 24 to obtain thelicense 16. The browser 62 may have pre-defined specifications, such asfor example screen size, and the license server 24 therefore may berequired to provide web pages designed with such specifications in mind.In particular, the web pages as they appear in the browser 62 may berequired to have a look and feel or style that is consistent.Accordingly, the user is not jarred by a web page having an unusualappearance in the browser 62 as hosted by the rendering application 34.Of course, the browser 62 and the web pages may have any particularspecifications or style or no such specifications or style at allwithout departing from the spirit and scope of the present invention.

[0278] Once the user and license server 24 have agreed to the terms ofthe license 16, such license 16 is delivered back to and received by thecomputing device 14 (step 1421). Such license 16 may be delivered to andreceived by the DRM system 32 directly, or indirectly by way of thebrowser 62, and the DRM system 32 appropriately stores the receivedlicense 16 in the license store 38 (step 1423). The DRM system 32 thennotifies the rendering application 34 that the license 16 has beenreceived or the rendering application determined from the DRM system 32that the license 16 has been received (step 1425), and the renderingapplication 34 may then shut down the hosted browser 62 (step 1427).

[0279] The particular mechanism for shutting down the browser 62 mayinvolve a ‘PLAY’ selection button on the browser 62, and the shuttingdown of the browser as at step 1427 occurs after the user actuates such‘PLAY’ button (step 1429). Of course, any other appropriate shut downmechanism may be employed without departing from the spirit and scope ofthe present invention. The rendering of the content 12 by the renderingapplication 34 may then proceed based on the accessed license 16 in theDRM system 32 in the manner discussed above (step 1409). Alternatively,the rendering application 34 may automatically shut down the browser 62and proceed to render the content 12.

[0280] In one embodiment of the present invention, prior to hosting thebrowser 62, the rendering application 34 prompts the DRM system 32 toattempt to silently acquire the license 16 from the license server 24without the need to bother the user (step 1431). As may be appreciated,the DRM system 32 can silently acquire the license 16 without help fromthe user only if the DRM system 32 has all information required by thelicense server 24. Such required information of course includes theinformation discussed above in connection with FIG. 7 and licenseacquisition. Such required information may also include user-relatedinformation, payment information, and the like. Preferably, the DRMsystem 32 has access to such required information. For example, suchrequired information or at least a portion thereof may already be storedin the state store 40 or another location accessible by the DRM system32. Especially in the case of more sensitive information such as paymentinformation, the user may be given the option to allow the DRM system 32to transmit such sensitive information to the license server 24 in asilent and automatic manner.

[0281] The DRM system 32 may perform silent acquisition as a matter ofcourse, or only as a user-selectable option. In the latter case, if theuser de-selects silent license acquisition, no such silent licenseacquisition is in fact attempted. Assuming that silent licenseacquisition is to be attempted, it is to be understood that such attemptat silent license acquisition may not succeed if, for example, the DRMsystem 32 cannot provide appropriate information to the license server24, or if the license server 24 refuses to allow a silent licenseacquisition.

[0282] Thus, in the course of attempting silent license acquisition, adetermination is made of whether such silent license acquisition hassucceeded (step 1433). If so, the rendering of the content 12 by therendering application 34 may then proceed based on the accessed license16 in the DRM system 32 in the manner discussed above (step 1409). Ifnot, the DRM system 32 notifies the rendering application 34 or therendering application 34 polls the DRM system 32 to gain knowledge ofthe failure to silently acquire a license 16, and the renderingapplication 34 may then proceed to host the browser 62 as at step 1415and as was discussed above.

[0283] Since silent license acquisition by way of the DRM system 32 andbrowser-enabled license acquisition by way of the browser 62 may behandled differently by the license server 24, it is to be appreciatedthat the license server 24 may be accessed by way of different siteidentifiers depending upon the mode of license acquisition. For example,during silent license acquisition, the DRM system 32 may employ a firstsite identifier (URL1 in FIG. 13) as obtained from the content package12 p, and during browser-enabled license acquisition, the browser 62 mayemploy a second site identifier (URL2 in FIG. 13) as obtained from thecontent package 12 p. As discussed above at step 1413, such second siteidentifier may be provided by the DRM system 32 to the browser 62 ashosted by the rendering application 34.

[0284] In one embodiment of the present invention, the renderingapplication 24 includes a status display portion 64 that displays statusinformation relating to the license acquisition process, and especiallythe license acquisition process as it relates to silent licenseacquisition as discussed above. Of course, such displayed statusinformation in the status display portion 64 may also relate to licenseacquisition by way of the hosted browser 62 as discussed above withoutdeparting from the spirit and scope of the present invention.

[0285] Such status information may for example comprise written and/orpictorial information informing the user that the license server 24 hasbeen contacted, that system and/or user information is being transmittedto the license server 24, that the requested license 16 is beingreceived from the license server 24, that the license server 24 hasrefused to issue a license 16, etc. Thus, and importantly, the user isnot left to wonder about the status of the license acquisition process,and therefore does not become frustrated due to the lack of such status.As may be appreciated, such frustration can easily arise in the user,especially in the case where the license acquisition process takes morethan a few seconds.

[0286] Especially in the case of silent license acquisition, the DRMsystem 32 may periodically check with the license server 24 for status,automatically receive status from the license server 24, and/or merelydetect when the requested license 16 is received and stored in thelicense store 38, among other things, and report relevant statusinformation based thereon to the rendering application 34 for display inthe status portion 64. Alternatively, the rendering application 34 mayperiodically poll the DRM system 32 for such relevant statusinformation. Importantly, by having the DRM system 32 notify therendering application 34 that the license 16 has been delivered, or byhaving the rendering application 34 poll the DRM system 32 to determinethat the license 16 has been delivered, such rendering application 34may then automatically begin to render the corresponding content 12based on the newly acquired license 16.

CONCLUSION

[0287] The programming necessary to effectuate the processes performedin connection with the present invention is relatively straight-forwardand should be apparent to the relevant programming public. Accordingly,such programming is not attached hereto. Any particular programming,then, may be employed to effectuate the present invention withoutdeparting from the spirit and scope thereof.

[0288] In the foregoing description, it can be seen that the presentinvention comprises a new and useful enforcement architecture 10 thatallows the controlled rendering or playing of arbitrary forms of digitalcontent 12, where such control is flexible and definable by the contentowner of such digital content 12. Also, the present invention comprisesa new useful controlled rendering environment that renders digitalcontent 12 only as specified by the content owner, even though thedigital content 12 is to be rendered on a computing device 14 which isnot under the control of the content owner. Further, the presentinvention comprises a rendering application 34 that supervises andcontrols the license acquisition process and in particular presents thelicense acquisition process to the user within the context of therendering application 34. Thus, the user is not confused or upset at thesudden appearance of a web page in a browser. Instead, the user ispresented with an overall seamless user experience.

[0289] It should be appreciated that changes could be made to theembodiments described above without departing from the inventiveconcepts thereof. It should be understood, therefore, that thisinvention is not limited to the particular embodiments disclosed, but itis intended to cover modifications within the spirit and scope of thepresent invention as defined by the appended claims.

1. A method of acquiring a digital license that authorizes rendering of corresponding digital content, the license to be acquired upon a rendering application on a computing device requesting a digital rights management (DRM) system on the computing device for authorization for such rendering based on such license and upon the DRM system notifying the rendering application that such license is not available on the computing device, the method comprising: hosting, by the rendering application, a browser; causing, by the rendering application, the browser to navigate to a license server; allowing a user to communicate with the license server by way of the hosted browser to acquire the license; receiving the license from the license server; and shutting down, by the hosting rendering application, the hosted browser upon receiving the license.
 2. The method of claim 1 comprising causing the browser to navigate to a license server based on information received by the rendering application from the DRM system.
 3. The method of claim 1 comprising receiving information necessary to acquire the license including a site identifier identifying a license server and causing the browser to navigate to the license server based on the site identifier.
 4. The method of claim 1 comprising hosting, by the rendering application, a browser that is initiated by the rendering application, under the control of such rendering application, and viewed within the context of the rendering application.
 5. The method of claim 1 comprising hosting a browser having pre-defined specifications, and receiving information from the license server designed in accordance with such specifications.
 6. The method of claim 5 comprising hosting a browser having pre-defined view width and view height, and receiving information from the license server designed in accordance with such view width and view height.
 7. The method of claim 1 comprising receiving the license from the license server directly to the DRM system.
 8. The method of claim 1 further comprising storing the received license in a license store of the DRM system.
 9. The method of claim 1 comprising shutting down the hosted browser upon a user actuation.
 10. The method of claim 1 comprising shutting down the hosted browser upon receiving notification that the license has been received.
 11. The method of claim 10 comprising shutting down the hosted browser upon receiving notification from the DRM system that the license has been received.
 12. The method of claim 1 further comprising proceeding, by the rendering application, to render the content based on the received license.
 13. A computer-readable medium having computer-executable instructions thereon for performing the method of claim
 1. 14. A method of acquiring a digital license that authorizes rendering of corresponding digital content, the license to be acquired upon a rendering application on a computing device requesting a digital rights management (DRM) system on the computing device for authorization for such rendering based on such license, the method comprising: attempting, by the DRM system, to silently acquire the license from a license server without the intervention of a user; and if the attempt to silently acquire the license fails, allowing a user to attempt to acquire the license from a license server by way of a browser hosted by the rendering application.
 15. The method of claim 14 wherein allowing a user to attempt to acquire the license from a license server by way of a browser hosted by the rendering application comprises: hosting, by the rendering application, a browser; causing, by the rendering application, the browser to navigate to a license server; allowing a user to communicate with the license server by way of the hosted browser to acquire the license; receiving the license from the license server; and shutting down, by the hosting rendering application, the hosted browser upon receiving the license.
 16. The method of claim 14 comprising: determining, by the DRM system, during the attempted silently license acquisition, that the DRM system does not have available thereto all information required by the license server; and allowing the user to attempt to acquire the license from a license server by way of a browser hosted by the rendering application.
 17. The method of claim 14 comprising: determining, by the DRM system, during the attempted silently license acquisition, that the license server does not permit silent license acquisition; and allowing the user to attempt to acquire the license from a license server by way of a browser hosted by the rendering application.
 18. The method of claim 14 comprising: determining that the user does not permit silent license acquisition; and allowing the user to attempt to acquire the license from a license server by way of a browser hosted by the rendering application.
 19. The method of claim 14 comprising: attempting, by the DRM system, to silently acquire the license from a license server by way of a first site identifier therefor; and if the attempt to silently acquire the license fails, allowing a user to attempt to acquire the license from a license server by way of a second identifier therefor different from the first identifier.
 20. A computer-readable medium having computer-executable instructions thereon for performing the method of claim
 14. 21. A method of acquiring a digital license that authorizes rendering of corresponding digital content, the license to be acquired upon a rendering application on a computing device requesting a digital rights management (DRM) system on the computing device for authorization for such rendering based on such license, the method comprising: attempting, by the DRM system, to silently acquire the license from a license server without the intervention of a user; receiving, by the rendering application from the DRM system, status information relating to the attempted license acquisition by the DRM system; and displaying, by the rendering application, the received status information in a status display portion of the rendering application.
 22. The method of claim 21 further comprising, if the attempt to silently acquire the license fails, allowing a user to attempt to acquire the license from a license server by way of a browser hosted by the rendering application.
 23. The method of claim 21 comprising displaying the received status information in the status display portion of the rendering application in at least one of a written and a pictorial form.
 24. A computer-readable medium having computer-executable instructions thereon for performing the method of claim
 21. 25. A computing device having operating thereon a rendering application for rendering digital content and a digital rights management (DRM) system for authorizing such rendering based on a corresponding digital license, the rendering application and the DRM system for effectuating acquisition of such license upon the rendering application requesting the DRM system for authorization for such rendering based on such license and upon the DRM system notifying the rendering application that such license is not available on the computing device, the rendering application hosting a browser and causing the browser to navigate to a license server to allow a user to communicate with the license server by way of the hosted browser to acquire the license, the rendering application shutting down the hosted browser upon receiving the license from the license server.
 26. The computing device of claim 25 wherein the rendering application causes the browser to navigate to a license server based on information received by the rendering application from the DRM system.
 27. The computing device of claim 25 wherein the rendering application receives information necessary to acquire the license including a site identifier identifying a license server, and causes the browser to navigate to the license server based on the site identifier.
 28. The computing device of claim 25 wherein the rendering application hosts a browser that is initiated by the rendering application, under the control of such rendering application, and viewed within the context of the rendering application.
 29. The computing device of claim 25 wherein the rendering application hosts a browser having pre-defined specifications and receives information from the license server designed in accordance with such specifications.
 30. The computing device of claim 29 wherein the rendering application hosts a browser having pre-defined view width and view height, and receives information from the license server designed in accordance with such view width and view height.
 31. The computing device of claim 25 wherein the DRM system receives the license from the license server directly.
 32. The computing device of claim 31 wherein the DRM system stores the received license in a license store of the DRM system.
 33. The computing device of claim 25 wherein the rendering application shuts down the hosted browser upon a user actuation.
 34. The computing device of claim 25 wherein the rendering application shuts down the hosted browser upon receiving notification that the license has been received.
 35. The computing device of claim 34 wherein the rendering application shuts down the hosted browser upon receiving notification from the DRM system that the license has been received.
 36. The computing device of claim 25 wherein the rendering application proceeds to render the content based on the received license.
 37. A computer-readable medium having computer-executable instructions thereon for performing the method of claim
 25. 38. A computing device having operating thereon a rendering application for rendering digital content and a digital rights management (DRM) system for authorizing such rendering based on a corresponding digital license, the rendering application and the DRM system for effectuating acquisition of such license upon the rendering application requesting the DRM system for authorization for such rendering based on such license and upon the DRM system determining that such license is not available on the computing device, the DRM system attempting to silently acquire the license from a license server without the intervention of a user, and, if the attempt to silently acquire the license fails, the rendering application hosting a browser and allowing a user to attempt to acquire the license from a license server by way of the hosted browser.
 39. The computing device of claim 38 wherein the rendering application allows a user to attempt to acquire the license from a license server by hosting a browser, causing the browser to navigate to a license server, allowing a user to communicate with the license server by way of the hosted browser to acquire the license, and shutting down the hosted browser upon receiving the license from the license server.
 40. The computing device of claim 38 wherein the DRM system determines during the attempted silently license acquisition that the DRM system does not have available thereto all information required by the license server; and the rendering application thereafter allows the user to attempt to acquire the license from a license server by way of a browser hosted by the rendering application.
 41. The computing device of claim 38 wherein the DRM system determines during the attempted silently license acquisition that the license server does not permit silent license acquisition, and the rendering application thereafter allows the user to attempt to acquire the license from a license server by way of a browser hosted by the rendering application.
 42. The computing device of claim 38 wherein the DRM system determines during the attempted silently license acquisition that the user does not permit silent license acquisition, and the rendering application thereafter allows the user to attempt to acquire the license from a license server by way of a browser hosted by the rendering application.
 43. The computing device of claim 38 wherein the DRM system attempts to silently acquire the license from a license server by way of a first site identifier therefor, and if the attempt to silently acquire the license fails, the rendering application allows a user to attempt to acquire the license from a license server by way of a second identifier therefor different from the first identifier.
 44. A computer-readable medium having computer-executable instructions thereon for performing the method of claim
 38. 45. A computing device having operating thereon a rendering application for rendering digital content and a digital rights management (DRM) system for authorizing such rendering based on a corresponding digital license, the rendering application and the DRM system for effectuating acquisition of such license upon the rendering application requesting the DRM system for authorization for such rendering based on such license and upon the DRM system determining that such license is not available on the computing device, the DRM system attempting to silently acquire the license from a license server without the intervention of a user, the rendering application receiving from the DRM system status information relating to the attempted license acquisition by the DRM system and displaying the received status information in a status display portion of the rendering application.
 46. The computing device of claim 45 wherein if the attempt to silently acquire the license fails, the rendering application allows a user to attempt to acquire the license from a license server by way of a browser hosted by the rendering application.
 47. The computing device of claim 45 wherein the rendering application displays the received status information in the status display portion of the rendering application in at least one of a written and a pictorial form.
 48. A computer-readable medium having computer-executable instructions thereon for performing the method of claim
 45. 49. A method for a rendering application on a computing device to effectuate acquiring a digital license that authorizes rendering of corresponding digital content, the license to be acquired upon the rendering application requesting a digital rights management (DRM) system on the computing device for authorization for such rendering based on such license and upon the DRM system notifying the rendering application that such license is not available on the computing device, the method comprising: hosting a browser; causing the browser to navigate to a license server; allowing a user to communicate with the license server by way of the hosted browser to acquire the license; and shutting down, by the hosting rendering application, the hosted browser upon reception of the license from the license server.
 50. The method of claim 49 comprising causing the browser to navigate to a license server based on information received by the rendering application from the DRM system.
 51. The method of claim 49 comprising receiving information necessary to acquire the license including a site identifier identifying a license server and causing the browser to navigate to the license server based on the site identifier.
 52. The method of claim 49 comprising hosting a browser that is initiated by the rendering application, under the control of such rendering application, and viewed within the context of the rendering application.
 53. The method of claim 49 comprising hosting a browser having pre-defined specifications, and receiving information from the license server designed in accordance with such specifications.
 54. The method of claim 53 comprising hosting a browser having pre-defined view width and view height, and receiving information from the license server designed in accordance with such view width and view height.
 55. The method of claim 49 comprising shutting down the hosted browser upon a user actuation.
 56. The method of claim 49 comprising shutting down the hosted browser upon receiving notification that the license has been received.
 57. The method of claim 56 comprising shutting down the hosted browser upon receiving notification from the DRM system that the license has been received.
 58. The method of claim 49 further comprising proceeding to render the content based on the received license.
 59. A computer-readable medium having computer-executable instructions thereon for performing the method of claim
 49. 60. A method for a rendering application on a computing device to effectuate acquiring a digital license that authorizes rendering of corresponding digital content, the license to be acquired upon the rendering application requesting a digital rights management (DRM) system on the computing device for authorization for such rendering based on such license, the method comprising: allowing the DRM system to attempt to silently acquire the license from a license server without the intervention of a user; and if the attempt to silently acquire the license fails, allowing a user to attempt to acquire the license from a license server by way of a browser hosted by the rendering application.
 61. The method of claim 60 wherein allowing a user to attempt to acquire the license from a license server by way of a browser hosted by the rendering application comprises: hosting a browser; causing the browser to navigate to a license server; allowing a user to communicate with the license server by way of the hosted browser to acquire the license; and shutting down the hosted browser upon reception of the license from the license server.
 62. A computer-readable medium having computer-executable instructions thereon for performing the method of claim
 60. 63. A method for a rendering application on a computing device to effectuate acquiring a digital license that authorizes rendering of corresponding digital content, the license to be acquired upon the rendering application requesting a digital rights management (DRM) system on the computing device for authorization for such rendering based on such license, the method comprising: allowing the DRM system to attempt to silently acquire the license from a license server without the intervention of a user; receiving from the DRM system status information relating to the attempted license acquisition by the DRM system; and displaying the received status information in a status display portion of the rendering application.
 64. The method of claim 63 further comprising, if the attempt to silently acquire the license fails, allowing a user to attempt to acquire the license from a license server by way of a browser hosted by the rendering application.
 65. The method of claim 63 comprising displaying the received status information in the status display portion of the rendering application in at least one of a written and a pictorial form.
 66. A computer-readable medium having computer-executable instructions thereon for performing the method of claim
 63. 67. A computer-readable medium having computer-executable instructions thereon for performing a method of acquiring a digital license that authorizes rendering of corresponding digital content, the license to be acquired upon a rendering application on a computing device requesting a digital rights management (DRM) system on the computing device for authorization for such rendering based on such license, the instructions being organized into modules comprising: a first module for attempting, by the DRM system, to silently acquire the license from a license server without the intervention of a user; and a second module for, if the attempt to silently acquire the license fails, allowing a user to attempt to acquire the license from a license server by way of a browser hosted by the rendering application.
 68. The medium of claim 67 wherein the second module allows a user to attempt to acquire the license from a license server by way of a browser hosted by including: a first sub-module for hosting, by the rendering application, a browser; a second sub-module for causing, by the rendering application, the browser to navigate to a license server; a third sub-module for allowing a user to communicate with the license server by way of the hosted browser to acquire the license; a fourth sub-module for receiving the license from the license server; and a fifth sub-module for shutting down, by the hosting rendering application, the hosted browser upon receiving the license.
 69. The medium of claim 67 comprising: a third module for determining, by the DRM system, during the attempted silently license acquisition, that the DRM system does not have available thereto all information required by the license server; and a fourth module for allowing the user to attempt to acquire the license from a license server by way of a browser hosted by the rendering application.
 70. The medium of claim 67 comprising: a third module for determining, by the DRM system, during the attempted silently license acquisition, that the license server does not permit silent license acquisition; and a fourth module for allowing the user to attempt to acquire the license from a license server by way of a browser hosted by the rendering application.
 71. The medium of claim 67 comprising: a third module for determining that the user does not permit silent license acquisition; and a fourth module for allowing the user to attempt to acquire the license from a license server by way of a browser hosted by the rendering application.
 72. The medium of claim 67 comprising: a first module for attempting, by the DRM system, to silently acquire the license from a license server by way of a first site identifier therefor; and a second module for, if the attempt to silently acquire the license fails, allowing a user to attempt to acquire the license from a license server by way of a second identifier therefor different from the first identifier. 